Related
I see posts about cyanogen no longer officially supporting the vibrant, and although I DO like CM, I don't support the concept that it should be the end all be all of rom designs. Many of the custom roms I've seen on XDA offer specialized mods that may never make it to the CM roms..
That said, I haven't developed any roms, but I have seen plenty of people claim they are willing to help and have varying levels of experience. I've downloaded the source code for ICS and am wanting to find any devs or people willing to go through the learning process to try to make ICS work for vibrants.
I saw this thread [DEV] ICS port for I9000/I9000B - ALPHA (ICS sources) - work in progress and realize perhaps we can port that over if they get it working, but we would still need to organize people who are willing to work on some sort of project.
Our device is far from defunct, there are still people modding the OG droid that has far inferior specs, so all we need are people who are willing to keep the vibrant alive. It is a good phone, and should have community support until it truly IS defunct.
Thoughts, volunteers, devs have any input? Please no flaming, just because some may not think this is worthwhile or even possible, I know there are many that would appreciate the possibilites that exist.
We have a good port now....Check in the devolvement forums.
Sent from my SGH-T959 using XDA App
This is the one im using now http://forum.xda-developers.com/showthread.php?t=1362961 it has a few bugs but all in all its pretty stable.
its amazing
Now recruiting everyone, and i mean everyone from devs, themers, rom porters, testers, everyday users, everyone that loves their old phone and wants to see the development live on.
The only requirement is to work toward the common goal of seeing our old HTC devices live on.
Team Legacy: Greasing the Wheels for HTC Android Legacy Devices.
We may not have the newest, spankiest devices, but by god we just wont quit.
If anyone can think up a logo or a new motto, please do.
Between the eris, the hero, and the heroc, we are all in this together.
Great idea. At this stage there are so few developers working on legacy devices, with some devices having no active development at all.
It makes sense to have a 'pool' of Developers brought together; able to work on multiple devices.
Give people the option to donate a second-hand device to 'Team Legacy.' This could be done by either someone sending a device they no longer want, or starting a fund and having people donate what they can to buy a specific device for the team. That device could even be circulated among them by post if necessary.
Progress might take months instead of weeks, but at least we would have progress!
Motto idea: Development requires skill; not new hardware.
I'm in this! We should keep the old devices pumping!
Reviving old good roms, building on stock, sense, froyo, gb, ics, it doesn't matter, as long as we have something to flash - everyone is happy!
I will soon make a sense 2.0 rom (stock one, with lots of customizations and tweaks that hopefully will make the greatest sense rom stock ever) and I will need testers and/or developers/modders that want to give an idea or a mod to this project!
I'd love to be a part of this, and with my new CM9 rom, i think we have a stable and fast ICS rom for all legacy devices
And ill be sure to port over your paranoid android rom and add the tweaks from my CM9 rom to boost speed significantly!
So who's in team legacy so far?
Also i have an extra htc hero gsm if anyone would be willing to trade for a hero cdma or Eris?
jordfaz said:
I'd love to be a part of this, and with my new CM9 rom, i think we have a stable and fast ICS rom for all legacy devices
And ill be sure to port over your paranoid android rom and add the tweaks from my CM9 rom to boost speed significantly!
So who's in team legacy so far?
Also i have an extra htc hero gsm if anyone would be willing to trade for a hero cdma or Eris?
Click to expand...
Click to collapse
Anyone who wants to join us!
You port paranoid android, I'll port next week the Miui 4.0.4 xD!
1ceb0x said:
Anyone who wants to join us!
You port paranoid android, I'll port next week the Miui 4.0.4 xD!
Click to expand...
Click to collapse
Will do
In my opinion this idea needs to be cross-posted for all HTC Android Legacy Devices to get maximum attention and to attract contributors to the project.
It would be also great to see this stickied in the Development section for all those devices.
lost101 said:
In my opinion this idea needs to be cross-posted for all HTC Android Legacy Devices to get maximum attention and to attract contributors to the project.
It would be also great to see this stickied in the Development section for all those devices.
Click to expand...
Click to collapse
+1
This would be great for all armv6 devices
We could use aroma installer in order to get one rom booting on several devices, this would mean we have more devs working on the same rom
I could create the aroma scripts with help from whoshotjr2006 regarding porting help.
jordfaz,
that was exactly what i was thinking of when i posted this lol. aroma is one hell of a tool, and if we could create 1 rom instead of 3, and just use aroma in order to make it work on all 3 devices, then that would be one heck of an ideal situation.
1ceb0x, jordfaz and lost101, welcome to Team Legacy!
benjamingwynn had posted .sense a while back, and while it didnt work on heroc, (not sure about hero) he had a great idea. one grand unifying rom that encompasses many devices, instead of 10 different roms for 10 different devices.
some early possible candidates for inclusion into Team Legacy are the G1, and the wildfire(buzz), and we already have eris, hero and heroc.
Also the way i see it is we already have many honorary members, such as the guys we ported from. Membership is just a matter of being a team player. Everyone that uses our devices in any way is a member already, we all just didnt know it until now lol.
As a policy, i would like to have open arms for any old devices, just so long as they have at least one guy to port/dev roms. that way since its hard for us to get other devices, everyone is represented in the process. Samsung, LG, Moto, they are all welcome.
It should work alright. We need a place to talk. Gtalk?
Sent from my HTC One V using xda app-developers app
I agree we need somewhere to talk. Gtalk will work ok for me.
sent from my heroc running cm7.2
whoshotjr2006 said:
I agree we need somewhere to talk. Gtalk will work ok for me.
sent from my heroc running cm7.2
Click to expand...
Click to collapse
I don't have Gtalk sorry
And has anyone created a logo for team legacy yet? I tried and failed :silly:
Im interested in joining Team Legacy. I have an HTC Hero GSM, im trying to port MIUI v4 on it, and later probably MIUI v3
welcome to team legacy! we are glad to have you. im cooking up something in the works that will hopefully help out the way roms are installed right now, and more details will come hopefully very soon.
any way you can contribute, we are glad to have you!
It would be cool to make a team legacy social group here on XDA, we had one on HTC Tattoo. So all devs can make a thread there on their alpha builds to be tested or ask for help off forums.
Team Legacy Official Social Group
http://forum.xda-developers.com/group.php?groupid=762
Join Away!
whoshotjr2006 said:
Team Legacy Official Social Group
http://forum.xda-developers.com/group.php?groupid=762
Join Away!
Click to expand...
Click to collapse
I am working for HTC Tattoo...and i just joined your group...currently im working on a SEMC port to HTC Tattoo and a REALLY need help...i hope u guys will help
I created an irc channel on freenode #team-legacy , should make it easy for all of us to communicate.
You guys are fookin awesome man
Sent from my Hero
Shelnutt2 said:
I created an irc channel on freenode #team-legacy , should make it easy for all of us to communicate.
Click to expand...
Click to collapse
How do i access it?
Having owned the International GS3 i9300 and expecting so much from a phone with such powerful and capable hardware, it was a shame to see all the major devs abandoning it because of crapsung's stubbornness with giving out Exynos and other hardware sources. Since its safe to say almost everyone buys the Nexus for dev support, it would be good to see some devs voicing their opinion about how easy it would be to, say port CM10 (or 10.1) to it. How 'open' is the hardware on the Nexus 4? With all the recent 'less than stellar' reviews about the phone (I already know the reviewers had pre-release firmwares), it would be good to know if custom kernels and such can bring out the full potential of the beast that is S4 Pro.
I am a complete n00b, so apologies if this is inappropriate in any way.
anirudh412 said:
Having owned the International GS3 i9300 and expecting so much from a phone with such powerful and capable hardware, it was a shame to see all the major devs abandoning it because of crapsung's stubbornness with giving out Exynos and other hardware sources. Since its safe to say almost everyone buys the Nexus for dev support, it would be good to see some devs voicing their opinion about how easy it would be to, say port CM10 (or 10.1) to it. How 'open' is the hardware on the Nexus 4? With all the recent 'less than stellar' reviews about the phone (I already know the reviewers had pre-release firmwares), it would be good to know if custom kernels and such can bring out the full potential of the beast that is S4 Pro.
I am a complete n00b, so apologies if this is inappropriate in any way.
Click to expand...
Click to collapse
Wrong section you should post in the question/answers section.
Anyway to answer your question Qualcomm is pretty much open with their processors and I don't believe there would be any problems building kernels and porting roms.
This is going to be locked / moved.
Nexus devices get CM10 very fast as you only need too add Cyanogenmod source merges and compile it to the Nexus 4 AOSP source and its good to go.
'In retrospect, I think this belongs to the general section! Derp! Can someone move it there?'
This was going to be my next post :angel:
anirudh412 said:
'In retrospect, I think this belongs to the general section! Derp! Can someone move it there?'
This was going to be my next post :angel:
Click to expand...
Click to collapse
It could of gone in either but I think it best suits the q&a section because you are specifically asking a question and you want an answer in return.
Wrong section, ib4tl
Edit: Also, just to put in something useful, this phone WILL be improved, if there are ANY software issues. This is the phone that will have the most dev support in years, with it's low price. In addition, CM isn't "ported", per say, it is built from source.
anirudh412 said:
'In retrospect, I think this belongs to the general section! Derp! Can someone move it there?'
This was going to be my next post :angel:
Click to expand...
Click to collapse
I asked a mod to move it.
anirudh412 said:
Having owned the International GS3 i9300 and expecting so much from a phone with such powerful and capable hardware, it was a shame to see all the major devs abandoning it because of crapsung's stubbornness with giving out Exynos and other hardware sources. Since its safe to say almost everyone buys the Nexus for dev support, it would be good to see some devs voicing their opinion about how easy it would be to, say port CM10 (or 10.1) to it. How 'open' is the hardware on the Nexus 4? With all the recent 'less than stellar' reviews about the phone (I already know the reviewers had pre-release firmwares), it would be good to know if custom kernels and such can bring out the full potential of the beast that is S4 Pro.
I am a complete n00b, so apologies if this is inappropriate in any way.
Click to expand...
Click to collapse
Since its a nexus device, the source tree is already in aosp so custom ROMs like cm10, aokp, etc will appear almost instantly. No need to do any major hacks get stuff fully working like other phones.. Same with kernels, the source will be available immediately, so there's no waiting for the new kernel sources (*COUGH COUGH * HTC)
Sent from my SGH-I747 using Tapatalk 2
I think molesarecoming is planning to bring ParanoidAndroid over to the Nexus 4
Seriously, I have no idea, came from an Amaze 4G with just the Android Development. At first I thought it was a Nexus thing, but the optimus G has two as well
Sent from my Nexus 4 using xda app-developers app
Basically everything in the original section is made from scratch, while in the android dev section its taken from the original section and modified.
It's more like this:
http://forum.xda-developers.com/showthread.php?t=1219612
So which would you say is better, more well rounded, and less buggy?
Original Development covers the whole spectrum. From barely works to just beautiful. If there are bugs the developer will squash the bugs. Development Forum is likely to have less bugs because they take the already good work and put in their stuffs. But if there is a bug, expect to wait a while for it to be addressed.For a good phone with a lot of awesome developers as the Nexus 4, Original Development is the way to go. If you're just looking for small mods, go to Development.
Thanks for the explanation.
On other question, does anyone know a guide explaining how trebuchet/launcher3 works and how to modified it?
I wanna learn how to code for android and add a few features.
Hello Everyone
I have come across device tree for Hima M9/CyanogenMod 12.1 with a custom Kernel. (If I'll tell you the name of either , you'd Google in a second)
The developer is a genius and trust me you'd see both of these within a month. Stay tuned for updates.
I can attach screenshots but I'd not post links as previous experiences that I had meant that people started troubling the developer and he quit the project all together. Respect the developers and read in my signature about development process and what it is actually like to be one.
This is just a confirmation and I can actually prove it to everyone who are interested.
I see many device tree updates every day so I am sure once CM12.1 is available officially, it'd open gates for all sorts of custom ROMs!
Attachments coming in few hours as I'm heading out
wow that would be awesome! cant wait to run a pure android rom on this beast
*all f***** fingers crossed*
Yay!
Sent from my LG-H811 using Tapatalk
Hnk1 said:
Hello Everyone
I have come across device tree for Hima M9/CyanogenMod 12.1 with a custom Kernel. (If I'll tell you the name of either , you'd Google in a second)
The developer is a genius and trust me you'd see both of these within a month. Stay tuned for updates.
I can attach screenshots but I'd not post links as previous experiences that I had meant that people started troubling the developer and he quit the project all together. Respect the developers and read in my signature about development process and what it is actually like to be one.
This is just a confirmation and I can actually prove it to everyone who are interested.
I see many device tree updates every day so I am sure once CM12.1 is available officially, it'd open gates for all sorts of custom ROMs!
Attachments coming in few hours as I'm heading out
Click to expand...
Click to collapse
The link below is to the thread which its being discussed in within m9 Q&A section. Rashid97 is the dev working on the project
http://forum.xda-developers.com/one-m9/help/cyanogenmod-12-12-1-htc-one-m9-t3069920
v1rk said:
The link below is to the thread which its being discussed in within m9 Q&A section. Rashid97 is the dev working on the project
http://forum.xda-developers.com/one-m9/help/cyanogenmod-12-12-1-htc-one-m9-t3069920
Click to expand...
Click to collapse
aaronrw said:
Yay!
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
sweetrobot said:
about ****ing time!!! so sick of the nonSense...
cm / aosp / aokp ftw.
paperweight for the last couple of months. tried a bunch of the existing roms, just not my cup of tea.
Click to expand...
Click to collapse
k1moe said:
wow that would be awesome! cant wait to run a pure android rom on this beast
*all f***** fingers crossed*
Click to expand...
Click to collapse
I am afraid that is not it what you are pointing out.
Here are the screenshots.
You can clearly see that how much commits are posted daily and it is going on at a very brisk rate. Cheer up everyone!
Request :
Just please do not trouble the developer if you find out who is he.
READ THIS HERE
Alternatively you can see more information in my signature!
Hnk1 said:
DEVELOPMENT PROCESS
INTRODUCTION
I am starting this forum in hope of educating my readers about ROM development according to my experiences. Further, I will highlight what is the usual developers' thought process before they decide to build a ROM for a specific device. The reasons why they usually choose a certain device or why they prefer one device over another would also be stated briefly. I also have intention of looking into ways how we can speed up ROM productions for any device and what you can do to play your part.
I UNDERSTAND YOUR FRUSTRATION FOR NO CUSTOM ROMS EVEN AFTER SOME MONTHS BUT THIS DOESNOT GIVE YOU THE RIGHT TO SPAM
I am sure many of you must be really disappointed by the lack of development for your device and I know this must be frustrating when we see other devices are getting ROMS so quickly. I know many are too excited when they find a little about any OTA/ Custom ROM and sharing such news is fully justified. However, it's beyond my logic & thinking why the forums are SPAMMED for any little information they might find anywhere regardless of their sources or if it has been ALREADY POSTED. I reckon many of these threads could have been avoided by simply searching in the forum.
ROM DEVELOPMENT
I can assure you that many develoeprs are working very hard to PORT and develop different ROMS for a device. However, the reason we can not see any CUSTOM roms till yet is due to complicated nature of a device itself.
Usually developers prefer a device which is :
1. Easy to work with, less complicated to code with or in other terms DEVELOPER friendly. For example, for a while I had a real issue with HTC phones as they have too many things to work with like Bootloader, S Lock, Radios, Hboot version etc while in Nexus devices you only need to unlock your device with one fastboot command. That's all and you are ready to flash ROMs.
2. Personal preference of Device. This simply means that we all have different tastes and thus we choose different devices. A certain developer might only work for a certain brand while other might work with few brands. This has nothing to do with anything but a personal choice.
3. A device that promises reward in terms of money/self satisfaction. Developers usually go for devices which have most active users so if their intention is also to get some money out of it in terms of donation, this will work well with devices which are more in number.
4. Knowledge about a certain brand more than another.
5. MONEY TO BUY A CERTAIN DEVICE/DEVICES. Suppose a developer wants to make ROMS for Xperia L/ SP/Z and Xperia U. Yet he only has 500 dollars to choose from. He then will have to make a choice between devices and this will eventually mean that not all of the devices get the same treatment. Money is the most decisive factor why a developer doesnot chose your device but rather another. For example purpose only, if I have to choose between devices, I might prefer SP over Xperia L as I can see more future of SP than Xperia L(I might be wrong).
6. Simply he bought a device or it is gifted/donated to him
SOME REQUESTS
Please STOP bugging developers by trivial questions. Just think how many other people ask the same question and it gets very frustrating to actually work on the device itself.
Every developer has a LIFE apart from developing ROMs. They also have a family, school, work, hobbies, bad days and so much like us. So they will do it when they feel like doing it. Just sit back and relax. Enjoy your device until developer releases the ROM for your device. Asking a REASONABLE question seems plausible but asking same questions/useless questions without using brains is just STUPID. Kindly refrain from that.
If you have seen a developer who has taken the initiative to work on your device , the best thing to do is to be patient. Let him concentrate. Spamming and spamming again won't help really.Yet some users start SPAMMING developers, their twitters, blogs and accounts. That's really sad. You can discuss on the forum what you think about it but IRKING developers isnot really cool.
WHAT CAN YOU DO TO HELP DEVELOPERS AND SEE CUSTOM ROMS.
1. Search the form first and look for answers. DON'T start new posts/questions/threads when it is ALREADY mentioned in some other section.
2. STOP PMing/SPAMING developers but rather ask a question WHICH havenot been asked before in the forum. Do not engage in the habit of making a new forum for everything. Try to keep threads as little as possible.
3. Follow developers and see what they have updated about on their official twitter,facebook,etc rather than bugging them on different forums/social websites.
4 DONATE THEM. DONATE THEM . DONATE THEM!
The amount of efforts they put, sitting for hours in front of their PCs and I know how frustrating it gets when you try to run commands and everything seems to work yet you can not boot up your ROM. And worse, you can not find WHY really. Just a change in line in build.prop results in failure of ROM to boot up and specially working from source to build ROM is really really tough. The best thing you can do is being supportive and patient !
A ROM development requires not just EXCESSIVE amount of hardwork, time, energy and dedication but also they need MONEY to actually buy devices and try it on. They are happy and encouraged to keep on developing ROMs when they see their efforts are not wasted and they are rewarded and respected for what they do.
SOME BASICS OF ROM DEVELOPMENT
Usually this is required to make a full custom ROM
Blobs which contain hardware information which comes from hardware manufacturer like Qualcomm in case of Snapdragon processors
A fully functional device tree
Latest Android source (Or the android version source you want to build for)
Specific Custom ROM coding which is based on Android Source
Usually a device tree and kernel tree is needed before custom roms can be made available. This is a long trial and error process in which every component of hardware is made functional as usually manufacturers do not provide any code for their devices and thus new code is to be written which is very frustrating and long process!
Click to expand...
Click to collapse
Hnk1 said:
I am afraid that is not it what you are pointing out.
Here are the screenshots.
You can clearly see that how much commits are posted daily and it is going on at a very brisk rate. Cheer up everyone!
Request :
Just please do not trouble the developer if you find out who is he.
READ THIS HERE
Alternatively you can see more information in my signature!
Click to expand...
Click to collapse
What i pointed is where the developer actually mentioned he his working on it and the link can be sourced by anyone, and people in that thread have been checking the github as mentioned. Theres now two threads on the discussion of cm12.1 which talk similar. All you are doing is not mentioning the dev based someone who used his work without his permission. Also to add the dev replied that thread to have to say they having working booting img just some features aren't working.
Link to his github for the current work
https://github.com/Hima-Dev/android_device_htc_hima-common
Thank GOD
---------- Post added at 01:33 PM ---------- Previous post was at 01:32 PM ----------
I'll be happy to donate
I'm really excited about this, because the person doing this is making amazing progress and at last count I want to say it was only Wi-Fi and one other thing not working with said developer already pretty certain that they know how to change that, it's just a lot of trial and error (any dev knows how frustrating it can be having to compile the source all over again to test a tiny change)
What this means for me, personally, is that I can do what I've done on past htc devices and knock out a fairly complete port of miui (some default miui stuff doesn't play nice during flash, like the camera app, so I'll likely include the stock m9 camera app as packaged for other phones so it doesn't rely on sense)
Anyway... ?
v1rk said:
What i pointed is where the developer actually mentioned he his working on it and the link can be sourced by anyone, and people in that thread have been checking the github as mentioned. Theres now two threads on the discussion of cm12.1 which talk similar. All you are doing is not mentioning the dev based someone who used his work without his permission. Also to add the dev replied that thread to have to say they having working booting img just some features aren't working.
Link to his github for the current work
https://github.com/Hima-Dev/android_device_htc_hima-common
Click to expand...
Click to collapse
Cheers for side information. I know the developer and I'm pretty sure you'd get a kernel and Cm12.1 pretty soon.
Actually I Would let the developers sort out their differences themselves, for me it is Cm12.1 coming pretty soon.
agentfusion said:
I'm really excited about this, because the person doing this is making amazing progress and at last count I want to say it was only Wi-Fi and one other thing not working with said developer already pretty certain that they know how to change that, it's just a lot of trial and error (any dev knows how frustrating it can be having to compile the source all over again to test a tiny change)
What this means for me, personally, is that I can do what I've done on past htc devices and knock out a fairly complete port of miui (some default miui stuff doesn't play nice during flash, like the camera app, so I'll likely include the stock m9 camera app as packaged for other phones so it doesn't rely on sense)
Anyway... ?
Click to expand...
Click to collapse
Whhhaaatttttt?!?!?! Miui?!?!?
Wait
Galaxysm said:
Whhhaaatttttt?!?!?! Miui?!?!?
Click to expand...
Click to collapse
Yeah. Once we have a reliable port of CM12, then porting other stuff is pretty easy. All I have to do is find a device that already has miui with the same resolution and dpi/ppi and port the assets over to the m9.
Preferably I'd like to port the miui patchrom so I can setup an automated build system to build a fresh copy every time aosp and miui are updated, but I don't have anywhere near enough time for that.
agentfusion said:
Yeah. Once we have a reliable port of CM12, then porting other stuff is pretty easy. All I have to do is find a device that already has miui with the same resolution and dpi/ppi and port the assets over to the m9.
Preferably I'd like to port the miui patchrom so I can setup an automated build system to build a fresh copy every time aosp and miui are updated, but I don't have anywhere near enough time for that.
Click to expand...
Click to collapse
Nice I can't wait!!
Nice to see this coming ... And for MIUI I haven't been able to use it since I change my original EVO ... It would be great to have it as an option ...
Great news
Daily reminder that CM12 is a desperately needed and coveted thingy for the m8+1.
Is it lollipop 5.1?
Sent from my HTC One M9 using XDA Free mobile app
vegetaleb said:
Is it lollipop 5.1?
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Cm12.1 is lolipop 5.1
Anyone knows the progress on this...
epedrosa said:
Anyone knows the progress on this...
Click to expand...
Click to collapse
Be patient. The OP says "within a month" and it has only been roughly 2 weeks