Related
I really don't want this to come across wrong, but I just have to say it.
Developers, I appreciate all your hard work. I understand this is all beta/test/etc. I understand it is free of cost, even to those who did donate to one dev or another. You do it because you want to, not because you have to.
But please, for the love of all that's good - keep an updated list of Known Issues!
It sucks having to read 50 pages of posts to try to figure out if a particular release is reliable or not, to find out if there's a key feature broken or buggy. What makes it worse is you can't tell when reading these threads which users are on which release, because many still post issues after they've been resolved. Others post things that aren't really "issues" but user error.
You know what your issues are, you read the threads and you fix the issues. But trying to find a decent rom to flash is very, very difficult when your OP says "No known problems" and the thread that follows show that to be very untrue. It generates a lot of extra posts with people posting things you already know about, and it generates a lot of bad will when someone flashes something only to find that there are a number of game breaking issues.
All it takes is to update a post, say #2, in your thread, with KNOWN ISSUES. Once you confirm a bug, whether you intend to fix it on your next release or not, add it to that thread. It helps you, as a dev keep track of the bug, and it helps potential downloaders know what bugs have been confirmed and make an educated decision as to whether they want to install your release.
Hiding known issues is something I don't think anyone does intentionally, but it feels that way sometimes. It feels like devs are in a popularity contest, and any admission of flaws in their particular ROM is a weakness. Well, to tell the truth, I and many others are sick of installing something that was CLAIMED to be working perfectly, only to have glaring problems that have been there for many versions.
For a civil and productive development community. Please. Be honest with your known issues. It will go a long way in building trust with the people who you're providing ROMs to, and will mean fewer posts for YOU to wade through of users reporting known issues, without having read 500 posts first.
I have a hard time believing that most devs actively hide them. Most of the time it's probably just a bit of laziness. But, yes, it would be helpful when comparing roms if the descriptions had a well-maintained list of active bugs.
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
The other issue is the people flashing these roms, coming from Eugene's to Whiskey to the ASOP roms may generate some ghosts in the software that the developers cannot duplicate themselves. I know that when I went with the TW 2.2 roms I had plenty of issues, more issues than I have had even when I was stock. Odining back to stock and reflashing the 4.2 TW fixed ALL my problems. Dont know what caused it but since I have flashed a couple of roms prior to that (no problems), I will assume there were some ghosts in my system. This is an example that unless a TW team member is holding MY phone and working on it, they may not be able to duplicate
They don't care to list them. It's beneath some of them.
Maybe AirBus should list "midair exploding engines" as a known issue too...
kponti said:
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
Click to expand...
Click to collapse
+1. Hell, at work I run a $100,000.00+ software suite and even that company won't do what the OP suggests!
If you have a problem with them stop using their roms go back to stock and see how much better theirs is even with a few bugs, not one of you has any right to complain. They do damn good work for free with some donations that do not come close to what they should be paid for it but they do not whine at all.
The problem I find is the "spammy" and useless comments average and pretentious users make which is both hard for the developer and the end user to read the threads. A dev releases a ROM and there is a guaranteed "Oh I can't wait to flash this" comment that will pop up. And there are some issues that are minor and are sometimes not related to the release that are posted and some pretentious loser who extends his ego by trying to make simple matters complicated. This forum didn't much of this problem before and I could quickly flash ROMs easily since I could clearly grasp the status on the ROM project.
I wish they would start a new thread with new releases. It's a pain to try to read through a 500 page thread, and you comments about this or that, and you have no idea which version the person is talking about. I gave up on custom roms and just using the leaked tmo 2.2, thanks for that Eugene
kponti said:
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
The other issue is the people flashing these roms, coming from Eugene's to Whiskey to the ASOP roms may generate some ghosts in the software that the developers cannot duplicate themselves. I know that when I went with the TW 2.2 roms I had plenty of issues, more issues than I have had even when I was stock. Odining back to stock and reflashing the 4.2 TW fixed ALL my problems. Dont know what caused it but since I have flashed a couple of roms prior to that (no problems), I will assume there were some ghosts in my system. This is an example that unless a TW team member is holding MY phone and working on it, they may not be able to duplicate
Click to expand...
Click to collapse
A $20 donation is not worth the risk of bricking a $550 phone just because they got "lazy" and didn't notify donators/downloaders of [a] potentially show-stopping issue.
Posted a new Thread in Dev section for the purpose of reporting issues. So if you have an issue please shoot it to me and I will post it in that thread.
Update: Here is the link for the WIKI page.
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
swehes said:
Posted a new Thread in Dev section for the purpose of reporting issues. So if you have an issue please shoot it to me and I will post it in that thread.
Click to expand...
Click to collapse
You are in a heap of trouble, a lot of people don't read, and you are gonna get 1000000000000000000000000000000000000000000000 repeats of the same issue.
"OMG! MY SD CAR DONES"T MOUNT< HELP ME!11!!111"
chui101 said:
I have a hard time believing that most devs actively hide them. Most of the time it's probably just a bit of laziness. But, yes, it would be helpful when comparing roms if the descriptions had a well-maintained list of active bugs.
Click to expand...
Click to collapse
The issue here is really that a forum is not the ideal place to manage software releases. A list of bugs emerges from community testing, but there's nowhere to "post" that list of issues, or attach it to a specific release. Since there's no way for the community to add such documentation, it falls on the ROM builder, who probably has other priorities.
This kind of project could be well served by using a real software project management software solution, such as say google code, which has an issue tracker and other useful features. But XDA does already give us a better tool than the forum - the XDA wiki!
I wish people would use the XDA wiki more extensively. This would be a good place to keep updated documentation such as this, without requiring the OP to keep a forum post updated with the latest findings. All the OP needs to do is link to the wiki page, and other people can help maintain it.
OK. Looking into Google Code.
(Update) So looking into the Google Code. What Licensing agreement are the ROMs under? Is it GPL v2 or v3 or another license?
swehes said:
OK. Looking into Google Code.
(Update) So looking into the Google Code. What Licensing agreement are the ROMs under? Is it GPL v2 or v3 or another license?
Click to expand...
Click to collapse
Depends on the project. The Linux kernel is GPLv2, so any kernels fall under that license. AOSP as a whole uses both GPL and apache code.
The issue with ROMs is that unless they're AOSP derived (like cyanogenmod) they often include binaries for which the license situation is murky at best, so google code isn't really an ideal fit for a "ROM" that's only ever released as a binary.
Really I was throwing google code out there as a well known example, there are tons of other ways to track issues. There are dedicated issue tracking systems such as trac, bugzilla, etc, but they require hosting. Most of the freely available hosted services require that you're running an open source project, which isn't necessarily true for the ROMs here.
IMO a serious project could very well benefit from such tools, but just using an XDA wiki page which community members can freely update is a great first step.
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
swehes said:
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
Click to expand...
Click to collapse
Not to be the "Spelling Nazi", and I am not even sure if you can change it, but it is "Kernel" not "Kernal". Also, the Dev on Team Whiskey is Sombionix, not Symbionix.
Otherwise, that looks like a great idea, and possible way of tracking things!
EDIT - I guess I could go ahead and make those tweaks, with it being a wiki and all couldn't I....
EDIT EDIT - Fixed it.
Stargazer3777 said:
Not to be the "Spelling Nazi", and I am not even sure if you can change it, but it is "Kernel" not "Kernal". Also, the Dev on Team Whiskey is Sombionix, not Symbionix.
Otherwise, that looks like a great idea, and possible way of tracking things!
EDIT - I guess I could go ahead and make those tweaks, with it being a wiki and all couldn't I....
EDIT EDIT - Fixed it.
Click to expand...
Click to collapse
Thanks. On both accounts.
Maybe this should be a post to Microsoft
To quote "there are known, unknowns and unknown, knowns and and even sometimes unknown,unknowns............but.........
Developers ----develop they do not become a bookkeeper of their development.........that is coordinating work...........good luck getting any developer in ANY Specialty to do that............. reporting bugs........
---Maybe this should be a post to Microsoft---
N8ter said:
A $20 donation is not worth the risk of bricking a $550 phone just because they got "lazy" and didn't notify donators/downloaders of [a] potentially show-stopping issue.
Click to expand...
Click to collapse
I have yet to see a REAL (completely dead) "bricked" vibrant from flashing a released Rom alone. I have seen a lot of user error cause boot loops or "soft-bricks" & HWL phones become unflashable because the end user didn't take the time to research though. As far as devs being "lazy" I dont really see that when the developer is coming here for us to tell him what else we find wrong. They are coding, you flash, you report back with a logcat. This is how development is made to my understanding. If ppl are to lazy to JUST do this then why shouldn't the developer discount long winded post or something they are not experiencing? If they know there is a bug its in the OP.
If you guys can change the interwebz & how 500 post per update are made completely useless please feel free to do so....
swehes said:
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
Click to expand...
Click to collapse
I think it's a pretty awesome start for sure
As a matter of personal taste, I think having an individual wiki page per ROM (with the known issues and other detailed info) might be nice, although I'm not sure what the policy on new pages is with the XDA wiki.
Speaking from professional experience, the most challenging aspect of any documentation system is always convincing people to use it. It's great to compile the information, but unless ROM builders and devs post a link to the wiki in the forum threads nobody will ever see it. Having good, community based documentation is a benefit to everybody though, so hopefully people will recognize the utility of it and encourage its growth!
i have been off from xda lately due to my admission process.logged in some time ago and saw that tytung has stopped support on xda and all his threads closed.why did this happen.can someone shed a light on this.
I am not offending anybody's decision. Just curious
Sent from my LG-P990 using xda premium
Whats happened to tytung
Ah that's a real shame. He put out some great ROMs but that's what happens when you don't obey the rules I guess. It's also nice to see that the mods are completely unbiased and won't give members preferential treatment due to their titles.
Oddly, tytung's threads were all closed apparently because he stated that he would not support them (although he did update). That is the reason given in @kinfauns closing post(s). This is the first time that I am aware of, of threads being closed due to lack of support by the dev. And I can see no rule which states that a dev MUST provide support.
In fact (some) support for these threads was being provided by members, and that is the case for many threads in which the developer/OP is no longer contributing to xda for whatever reason.
People using tytung's roms and needing support on xda, have no choice now but to seek support from "another place". Is it the intention of xda to force people to use a rival site? Or is it to stop people from promoting a rival site and therefore breaking xda rules?
I am just a bit confused as to why these threads were closed, any clarification would be appreciated.
I agree with Robbie p that the threads should be kept open for the users to help each other. Still if the mods are against it we can have a support thread in the general section.
Feels to lose a great dev
Sent from my LG-P990 using xda premium
It more looks like few moderators are simply emotionally hurt(you know what I mean) because Tytung's left.
No seriously, this is dumb. I can't post and provide ANY support for Tytungs ROM's(as many other people who got knowledge) because someone closed threads.
Even if there's no Tytung's, WE can provide basic support, for older iterations of ROM. There's much magic still to be done with HD2 android.
This is abusive. Mod responsible for this kind of damage should be punished.
Robbie P said:
Oddly, tytung's threads were all closed apparently because he stated that he would not support them (although he did update). That is the reason given in @kinfauns closing post(s). This is the first time that I am aware of, of threads being closed due to lack of support by the dev. And I can see no rule which states that a dev MUST provide support.
In fact (some) support for these threads was being provided by members, and that is the case for many threads in which the developer/OP is no longer contributing to xda for whatever reason.
People using tytung's roms and needing support on xda, have no choice now but to seek support from "another place". Is it the intention of xda to force people to use a rival site? Or is it to stop people from promoting a rival site and therefore breaking xda rules?
I am just a bit confused as to why these threads were closed, any clarification would be appreciated.
Click to expand...
Click to collapse
disclaimer ....the following reply is only my opinions
i agree with you ..there are many threads in the hd2 android dev section that should also be closed for no dev support ..in fact 98 percent of them shold be closed for lack of dev support
but what i think was the underlying problem was his links for roms went to links that generated money for him..
and i know if i was a dev that had 3 or 4 different rom threads i wouldnt wanna have to monitor 3 or 4 different q/a&t threads for those roms either that would make 6 or 8 threads a dev would have to monitor ,most dont have the time for that
hell you can see the activity in both sections has almost ground to a crawl ..its as if xda is slowly trying to fade out the hd2 android section
dont be surprised if you see some of the few remaining devs stop making roms and move on to something else
and those posts about about this being a dev thread please post in the q&a section blah blah blah are not helpfull to anyone and just clutter up the dev threads even more then offtopic posts do ..xda is trying to do much to late .ive been on xda since 2010 and there was never a problem with how the threads were maintained and handled ..
hell if the wanna do something good for the forum ..then they should change the signup rules and stop all the lazy people from just coming in new and immediatly posting about something that they couldve searched and read about but are to lazy to and want it all handed to them on a silver plate .....also they could remove people like abumaha who has never posted a single post about how good a rom is ..but always post how do i do this and why doesnt this rom work
ok im off my soapbox now
^ Still don't believe that abumaha is somehow still here :') But yeah I agree with Kam, things haven't been done completely correctly IMO.
Sent from my Nexus 4
+1 to kameirus i agree 143%
and abuhama.. just lol
on off topic on topic, if you want to find tytung , just google "forum tytung android" and you should find his forums
Everyone knows the mod's in question were just looking for an excuse they could give. He had dropped a new hd2 rom about 2 or 3 weeks prior. He had instructions on how to install it in post 1. Exactly how much "support" does a dev have to provide the users anyway? It was bs plain and simple....oh and if you looked at his status later they knocked him down to a "Senior Member"......I haven't seen any of the OTHER idle dev's getting their status pulled for being "idle".
As mentioned..they've done an excellent job of killing off the hd2 forum....there is almost no active development going on and the closest rom to tytungs still has a long list of things marked "not working". Tytung was also the only one producing recent jelly bean kernels with hd2 specific fixes so everything worked.
famewolf said:
1. Exactly how much "support" does a dev have to provide the users anyway? It was bs plain and simple....oh and if you looked at his status later they knocked him down to a "Senior Member"......I haven't seen any of the OTHER idle dev's getting their status pulled for being "idle".
Click to expand...
Click to collapse
now that was very low from them
famewolf said:
As mentioned..they've done an excellent job of killing off the hd2 forum....there is almost no active development going on and the closest rom to tytungs still has a long list of things marked "not working". Tytung was also the only one producing recent jelly bean kernels with hd2 specific fixes so everything worked.
Click to expand...
Click to collapse
That's right. all they're doing is killing the HD2 forums ...
i had reported all the "thread closed" posts by that mod, and i got:
tytung was not being picked on. This action was not taken lightly, or by kinfauns alone. tytung left us no choices.
Thank you,
mikef
XDA Senior Moderator
Click to expand...
Click to collapse
but in addition to close his threads, they also lowered him to senior member???
sorry if this is rude, but kinda reminds me of when a kid has his candy bar stoled, and he does everything to take revenge and take it back. enough for me
I do not know who made the decision re Tytung, but it was not made by a matured intellect. I have run systems since 1979 (with over 35 years as a senior networks systems/operations engineer) and have dealt with many experienced administrators, moderators and sysops, and the way this was handled shows nothing but ego-driven/threatened immaturity.
Shame on XDA.
MarkAtHome said:
I do not know who made the decision re Tytung, but it was not made by a matured intellect. I have run systems since 1979 (with over 35 years as a senior networks systems/operations engineer) and have dealt with many experienced administrators, moderators and sysops, and the way this was handled shows nothing but ego-driven/threatened immaturity.
Shame on XDA.
Click to expand...
Click to collapse
It does feel like some immature revenge.
It's not like only Tytung's got punished, but XDA users who were using his ROM's
I got unnerving thought, that this whole action is to bury HD2 development and make it Low legacy. While it's still in it's strenght despite old age
Shame on you XDA
MarkAtHome said:
I do not know who made the decision re Tytung, but it was not made by a matured intellect. I have run systems since 1979 (with over 35 years as a senior networks systems/operations engineer) and have dealt with many experienced administrators, moderators and sysops, and the way this was handled shows nothing but ego-driven/threatened immaturity.
Shame on XDA.
Click to expand...
Click to collapse
yeah! i just bet anyone who made this decision to port android and then build it from source and support a device that was never intended to run android in the first place!
Some of you may remember me from back in the "glory days" of Android on the HD2 when Cotulla and Darkstone were making the very first ROMs. I was here daily loading new builds, even when you could not turn the screen off one time or you'd get the SOD. That was when you could only do it through haret.
Fast forward a bit and we had magldr and cLK and where we really had a million options. Personally after a while I would pretty much stick with ACA on SD dual booted with WP7, but there were some really cool things out there to do. I spent many hours trying to troubleshoot people to flash hspl 2.08 or the right radio or to NOT flash certain radios etc. to get things going right.
Tytung was one of the greats as far as ROM and kernel development, and I am not prevaricating when I tell you that there is no XDA Staff on this site who does not respect what Tytung brought to the table. To put it in very simple yet eloquent terms: Dude had skill...
But our standing policy at XDA has always been that we do not keep open development threads with no support. Due to the fact that we just don't talk about individual dealings in public at XDA for privacy concerns we cannot get into specifics. But I can tell you that XDA has zero to gain from a developer such as that no longer supporting development threads here.
When something like this happens, there is no "victory" and no winner. sometimes things just don't work out for various reasons, and then sometimes things work out just fine in the end.
I can respect the disappointment and ambivalence on this matter, and believe me when I say that the HD2 is still a mighty device worthy of respect. I still own an HD2 along with all of the other devices I use, and it can still do some cool stuff. I wouldn't consider it a Legacy Device just yet!
orangekid said:
...
Click to expand...
Click to collapse
We understand all of this, but why close the threads? If you check the second or third page of the development forum and further, you can see many, and I mean MANY threads of ROMs which are either discontinued or whose developers moved onto other things, other devices. Yet, they are still open, and from time to time you see people bringing them back to surface and getting help. Just because the developer ceased support, it doesn't mean the threads should be closed. Delete his links, remove his other websites, just keep the threads open for members' discussion.
If the developer haven't requested a closure, I don't see a reason why they should be closed.
Marvlesz said:
We understand all of this, but why close the threads? If you check the second or third page of the development forum and further, you can see many, and I mean MANY threads of ROMs which are either discontinued or whose developers moved onto other things, other devices. Yet, they are still open, and from time to time you see people bringing them back to surface and getting help. Just because the developer ceased support, it doesn't mean the threads should be closed. Delete his links, remove his other websites, just keep the threads open for members' discussion.
If the developer haven't requested a closure, I don't see a reason why they should be closed.
Click to expand...
Click to collapse
When a developer publicly announces he will no longer follow the rules, no longer support his work posted here, and is actively trying to recruit members away from XDA to his new site, what do you really expect us to do? Cooperate with this effort? Seriously? Sure there are lots of other threads that have been effectively abandoned by their dev/OP when they moved on to a new device, but we simply do not have the luxury of time to go sift through thousands of threads to find them. When they are reported, we evaluate the situation and then act on it according to our guidelines.
Decisions like this are never made quickly, lightly, or on the fly by a single mod here. Now, I am closing this thread and I would appreciate it if no further threads were opened on this topic as it won't help to resolve the situation but will only make it worse.
You all do not know all of the facts in this situation, nor will you as we must respect tytung's privacy in his communications with us so we will not divulge them publicly. tytung is not banned or blacklisted, and is welcome to return here should he change his mind about following the rules. If he does not want to do that, it is entirely up to him.
Thank you,
mikef
XDA Senior Moderator
I have created this thread to prevent spamming the Android Development forum.
Starting point: http://forum.xda-developers.com/showpost.php?p=58117080&postcount=93
Originally Posted by BabelHuber
I honestly do not understand your whining here: We have:
- Pre-rooted stock ROMs for WIFI and LTE
- CM11 and CM12 for WIFI and LTE
- PAC ROM (4.4 and 5.0) for WIFI and LTE
- AOSP for LTE (WIFI will follow according to the guys from FreeXPERIA)
So nothing is "dead".
The Z2 tablet is not a best seller, it is a high-end Android tablet with a very limited user base. Of course devices which have sold an order of magnitude more like the Samsung Galaxy S5 or the HTC One M8 attract more developers, but then look at the forums for the Galaxy S5 Mini, where there is hardly any development at all. Compared to such devices we do very well here.
I personally am glad that we have good developers supporting our tablet and a range of custom ROMs to choose from and I am thankful for the ROMs we have and for the work the developers spend in their free time.
Finally, this is XDA here - if you think there are too few ROMs here feel free to make your own one instead of alienating the developers we have by complaining about their work.
Click to expand...
Click to collapse
Hi,
Waoh !
OK, sorry... I take it all back.
Did not thought my post would suggest such vehement reaction.
In fact, what did I wrote ?
Simply that on the whole channel dedicated to "Z2 Tablet Android development" there has not been a single post in over 3 weeks...
Which makes me fear that development is not really alive for a device I really like.
Does it deserve such reaction ?
Maybe. But I beg to differ...
I am not whining, I am not complaining... I was just stating.
That makes a difference to me. Maybe not to you...
Regards.
Click to expand...
Click to collapse
See, CM12 and Lollipop AOSP were updated just 2 days ago, on 2015-01-10. PAC was updated today, before it was updated on 2015-01-05. Yesterday, a new pre-rooted stock ROM for the SGP521 was posted.
Yet you ask if development is dead.
In my opinion, this is insulting the developers who do the work for us - for free, mind you!
I do not want to start a flame war or a non-technology-related discussion here. I merely want to point out that I do not share your view and that I am thankful for the ROMs we have.
Also I want to point out that I appreciate the work the developers do - we already have 'lost' a developer here in this forum who was alienated by some comments from certain members, and I think this shouldn't be repeated.
Hence I felt that I have to reply to your post to make the developers know that there are members on this board who do not share your view. Usually I simply ignore such posts to prevent spamming the forums, but I think your repeated complaints (no Apps2SD, no 4.4 AOSP, no new developments) warrant a reply.
BabelHuber said:
I have created this thread to prevent spamming the Android Development forum.
Starting point: http://forum.xda-developers.com/showpost.php?p=58117080&postcount=93
See, CM12 and Lollipop AOSP were updated just 2 days ago, on 2015-01-10. PAC was updated today, before it was updated on 2015-01-05. Yesterday, a new pre-rooted stock ROM for the SGP521 was posted.
Yet you ask if development is dead.
In my opinion, this is insulting the developers who do the work for us - for free, mind you!
I do not want to start a flame war or a non-technology-related discussion here. I merely want to point out that I do not share your view and that I am thankful for the ROMs we have.
Also I want to point out that I appreciate the work the developers do - we already have 'lost' a developer here in this forum who was alienated by some comments from certain members, and I think this shouldn't be repeated.
Hence I felt that I have to reply to your post to make the developers know that there are members on this board who do not share your view. Usually I simply ignore such posts to prevent spamming the forums, but I think your repeated complaints (no Apps2SD, no 4.4 AOSP, no new developments) warrant a reply.
Click to expand...
Click to collapse
you are both wrong, aosp daily builds are well, everyday, same with the official cm12 since, we get official, p.s. the current recovery in cm12 doesn;t flash, you have to downgrade the boot.img every time to the one from cm11 before updating
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
Hi,
I just thought it could be worth mentioning that there's a device request thread on Cyanogenmod forums for our beloved Idol 3 :
http://forum.cyanogenmod.org/topic/111850-alcatel-onetouch-idol-3-55/
May I suggest that everyone who wants a Cyanogen rom to be ported on our phones should take a minute to register there and add their voices to the request ?
There's already 24 posts in this thread
Already demanded it
Cool
Just made a post, but later found out that posting a request for CM does not guarantee anything. In the sticky it states
Now, what does this mean to you? First off, requesting anywhere in the CM forum, the CM Blog, or the Facebook/Google+/Twitter accounts for device XX to be supported is probably a waste of your time and anybody who reads said request. CyanogenMod does not work on device requests as there is no guaranteeing that a current CM maintainer is even interested in the device. Additionally, its not as simple as 'porting' code, the device trees must be coded from scratch and made to work with the AOSP sourced code and CM enhancements. This takes a large amount of time and effort, especially when the device's OEM fails to release the latest version of Android for it. Second, in hoping a worthy developer sees the post and decides to take up the project... well, that is probably just wishful thinking. Many developers do not like interacting with end users (too much finger pointing between both devs and users or anger directed at the devs for something working other than how the user expects - it happens far too often); because of that, many developers don't frequent the forum (or if they do, they only view the forums for the devices they maintain).
The best way to get a device official support is not requesting it from the CM team, but learning how to do it yourself or encouraging a maintainer of an unofficial build to submit their code for review. Many developers will work on unofficial ports on the xda-developers forum, so that would be the first place to check out. If there isn't any work currently being done, you can attempt it yourself. There is a pretty in-depth article in the wiki explaining a lot of the steps of porting a device (as the bottom of the wiki states, nothing can cover every single process of porting, but it is a really great start).
Click to expand...
Click to collapse
So it would need to be someone willing to take the time out to buy an Idol 3, if one has not done so already, and then port the code for our device out of their free time. And considering the userbase for this phone does not seem all that large to be noticed, I'm not sure if CM will work on our phones anytime soon.
Well thank you very much for your posts and your research.
I'm afraid you're right, but we had to ask
Let's not lose hope too soon anyway, the fact that the device request thread exist seems to be a good point. I don't know if any device had received a CM port because of this thread, but... why not ?
I've red that Alcatel and cyanogen had been in contact for a tablet. The project has been cancelled but this might suggest they could have access to resources that would ease their work (pilots ?).
Original rom on the idol is pretty much stock Android, this is a good thing too (well I'm not a developer but I guess it's easier when it's close to the original).
And, like you said, even if the user base is not that large, chances that someone from cyanogen got seduced by the idol (like we did) are still possible... (this is the moment where everybody crosses their fingers ).
Anyway thanks again !
The thread has now 31 posts (ah no, 32 webgaffeur just added his voice !)
Thanks to all the people that took some time to post there, let's not give it up : it's time to flood the forum !
i had posted the github with source for the phone but no one seems to respond not even one single admin? we can ask other devs crdroid pacrom dirty unicorns paranoid etc.
Alas, I think Brian is right : it's probably a waste of time posting on the device request thread
I checked devices with a lot more posts and views than ours and... nothing from a dev (like huyawei and Asus zenforce 5).
Asking to other rom devs will probably be useless also. Our only hope is that a competent developer buy an idol and start working on it... If this happens, I'm pretty sure he will share his work on XDA.
Well, meanwhile we already have root, twrp and xposed working, so I guess the best thing to do is to customise out phones till it suits our needs and that's all.
Let's hope also that Alcatel will continue to push updates (marshmallow ?)
Anyway thanks for your efforts Gecko.
Sorry, didn't mean to rain on anyones parade. Just wanted to let everyone know what the stickied thread on the CM forum for device requests stated. I'm not saying it won't ever happen, just that it might take some time to get a valued reputable dev who owns, or wouldn't mind purchasing the Idol 3 and working on it for us. Most dev's accept donations of devices that want development on from the users, so if we were able to locate and contact a reputable dev, asking them if we were to provide them with the device, would they mind porting or creating a ROM for it. It's worth a try. Maybe start a bounty or fundraiser etc. I myself do not know of any dev's that would be willing to work on this device as the ones I do know of have only worked on Samsung devices.
I don't know any dev at all
P.S. : thread has 34 answers now !
Cannadoux said:
I don't know any dev at all
P.S. : thread has 34 answers now !
Click to expand...
Click to collapse
theres always other devs like pacrom paranoid android crdroid and omnirom even dirtyy unicorns
Good news, it seems we haven't hoped for nothing : http://www.cyanogenmod.org/blog/releases-releases-releases-august-2015#comment-2229134454
Thanks to @purple.epod for posting the news.
From cirwl himself : "A couple of us have one, and kernel source was just released, so strong possibility of yes"
Yiiiihaaaa
this is great i hope that we get a nightly soon