Related
I've been working with a great group of developers over at PPC-geeks.com on the Titan bluetooth problems, and I'm proud to say that our efforts have been fruitful!
The History:
In case you didn't know, the Titan has had horrible official Bluetooth support, and even the custom roms only get it "partway" there.
HTC's latest CDMA device, the Touch, uses roughly the same hardware under the hood as the Titan, however their bluetooth worked flawlessly. So, clearly the hardware is capable, its a matter of running the proper software!
After many attempts at porting the Vogue (htc touch) Bluetooth drivers into any number and combination of titan roms, it was concluded that it is NOT the answer (sorry custel).
This was the first obvious approach, however every attempt had some problem or bug, or sometimes wouldn't even boot up!
So we took another approach...
The Solution:
Update the OS, but keep the drivers from an earlier build that had less new "issues" with BT. The 2.09 rom from sprint had stable bluetooth, however it had poor quality over the headset/handsfree profile. This was apparently NOT an issue with the drivers as much as it was an issue with how the OS handles them!
Replacing the OS with a ported AKU .7 from a Universal, and basing the rest of the rom on 2.09, we have what appears to be a release with stable, decent quality bluetooth that works as it should have out of the box!
More testing is needed, but it seems like the best build so far, and should be a strong candidate as a base rom for future customs.
What this fixes:
-No more poor BT quality
-No more random BT shutoffs
-No more system freezes when coming out of standby due to BT stack left on and disconnected
-No more D-pad lock issues
-Generally stable Bluetooth performance that works AS EXPECTED.
Known issues:
-Alarm Bug, which was and still is a part of 2.09
However, we're working on a fix for this.
Find it here:
ftp://ppcgeeks:[email protected]/Titan/Users/sfaure03/ithinkwegotsit.rar
(as of this writing, the ppcgeeks ftp and webserver have been hit pretty hard, and are timing out an awful lot, so if it doesn't work, try again later. Perhaps someone would like to mirror it somewhere?)
Special thanks to all who contributed to this effort, particularly PPC-geeks users Sfaure03, DogGuy, no2chem, jtrag, and all the others who tested, theorized, and gave sage advice.
Personal thanks to ImCoKeMaN, for explaining how things work and having the patience to answer bizzare questions from the rest of the group.
edit: whoops nevermind
I'm not expereinced enough in using this type of file - can you please tell me what is the procedure to install a .rar file into the phone.
its an .nbh file, rar is the compression method. Its like .zip, only you need winrar (or something compatible) to uncompress it.
there's a tutorial on ppc-geeks (which I should really post here as well) about how to unlock and flash custom firmwares on the titan.
you guys rock!
So installed this ROM a couple hours ago. So far the phone's working fine. Tested BT in my RAV4. Wife says it's much improved -- previously if I called from the carphone she'd known instantly and ask me to switch it off. Now she's says it's fine. (High praise indeed. )
So bottom line: quality issues appear much improved. Major kudos!
Update: maybe I was slightly hasty. So the phone sits in my pocket for a few hours. I press the power button to bring it out of sleep. Password screen takes 15 seconds to come up. Enter the password, Today screen takes 30 seconds. Click on the Voicemail link, get a message that the phone cannot make the call. (low RAM?) Nothing else (afaik) except SPB Mobile Shell running at the time.
Boom, soft reset. Is it the phone? Is it the ROM? Is it me?
Mirror at: http://rapidshare.com/files/71094429/ithinkwegotsit.rar.html
The ROM finally makes my BT usable, but is still quite choppy and compressed. Unfortunately not a true fix for my device.
But, kudos to the developers for getting it to be usable! Thanks!!! You clearly beat Sprint/HTC!
However, my RAZR2 and Touch still have much better BT, so will keep using them at least for awhile.
Will see if the 'official' Sprint ROM (1) actually happens, (2) truly fixes the problem. If not, then I'll use my Touch until the Treo 800w or Titan 2.0 come out and likely swap my Titan at that point.
Unfortunately, even if Sprint fixes BT, Titan 1.0 will never have adequate memory for WM6. Sadly, the lack of memory is an unfixable product design deficiency.
wsparvis said:
Unfortunately, even if Sprint fixes BT, Titan 1.0 will never have adequate memory for WM6. Sadly, the lack of memory is an unfixable product design deficiency.
Click to expand...
Click to collapse
Heh, I love it how everyone keeps badgering that.
Look, I don't want to take my thread off-course, but when WM6 was released, ALL DEVICES HAD ONLY 64MB!
It wasn't until recently that we really started to see 128mb become more standard. The Touch (vogue) is actually the first 128mb WM6 device I've ever put my hands on, and I've had WM6 running flawlessly on the last 5 or so devices I've owned.
So, don't tell me that this is a major unfixable product design deficiency. It'd be nice to have more memory so you can leave more stuff open, but if you're not new to this and know what you're doing, its perfectly acceptable.
::end rant::
Dishe said:
Heh, I love it how everyone keeps badgering that.
Look, I don't want to take my thread off-course, but when WM6 was released, ALL DEVICES HAD ONLY 64MB!
It wasn't until recently that we really started to see 128mb become more standard. The Touch (vogue) is actually the first 128mb WM6 device I've ever put my hands on, and I've had WM6 running flawlessly on the last 5 or so devices I've owned.
So, don't tell me that this is a major unfixable product design deficiency. It'd be nice to have more memory so you can leave more stuff open, but if you're not new to this and know what you're doing, its perfectly acceptable.
::end rant::
Click to expand...
Click to collapse
I have to agree here - the Cingular 8525 runs quite well with only 64MB of RAM (Other at work run it). My Titan runs quite well with only 64MB of RAM - HTC Home from the touch on the other hand makes it run like a three legged dog. Without the 3rd party plugins it zooms along quite well even with several apps running.
Dishe said:
Heh, I love it how everyone keeps badgering that.
Look, I don't want to take my thread off-course, but when WM6 was released, ALL DEVICES HAD ONLY 64MB!
It wasn't until recently that we really started to see 128mb become more standard. The Touch (vogue) is actually the first 128mb WM6 device I've ever put my hands on, and I've had WM6 running flawlessly on the last 5 or so devices I've owned.
So, don't tell me that this is a major unfixable product design deficiency. It'd be nice to have more memory so you can leave more stuff open, but if you're not new to this and know what you're doing, its perfectly acceptable.
::end rant::
Click to expand...
Click to collapse
OK - fair enough, my memory comment WAS off topic! BTW you introduced the word "major"; I never said it was major - just unfixable. And, yes, you're right - if you want to manually do the OS's job for it, there is an acceptable workaround.
Interesting, though, that you responded only to that one sentence out of five in my post, not the other four which stated that BT quality is poor/mediocre on my device (which is an improvement from the prior unlistenable state).
Anyway - what kind of success rate are you seeing from various forums with this ROM? I still suspect the problem is partially HW, and that BT on some devices (mine probably one of them) may be unfixable.
Dishe said:
After many attempts at porting the Vogue (htc touch) Bluetooth drivers into any number and combination of titan roms, it was concluded that it is NOT the answer (sorry custel).
This was the first obvious approach, however every attempt had some problem or bug, or sometimes wouldn't even boot up!
So we took another approach...
Click to expand...
Click to collapse
Why call out another developer? I fail to see how it was necessary. I'm assuming you have no life, and make roms for a living? I'll download whatever works; but because of your approach to criticize other people who try (which is EXACTLY what you do) to make something work, makes me not want to download your rom.
dishe is an such arrogant SOB, who think he's all that because he's creating ROM...well props to you that you do create rom...but its just people opinion/wish about having more ram (which is UNFIXABLE! on mogul)...you don't have to bash them for it...would u preferred an old style laptop/computer from the 2000's or newer/faster in 07's. However, you might be able to upgrade their RAM through hardware...but does HTC have such RAM upgrade for mogul!? anyways...i'm not hating on your work at all...but i just get disgusted when you go and ranted on someone post (n it was a valid post.)
ps. If you want to brag, make something that's useful w/o any glitches. Success at that then brag all you want, but at this moment you still using the public to test whatever ya doing. So stop tripping home boy.
Wow, I've heard of people venting on forums, but this is rediculous. Did you all have really bad days or something?
Look, there's a lot going on that doesn't take place on this forum. I used to be a big XDA-dev's fan, but unfortunatley I've found that there just isn't enough research and development for our particular device going on here, so I started broadening my horizons.
Maybe I didn't make it clear in the first post, but I didn't make this rom.
At least, not by myself. I worked with a team of people from other boards and we formed a group that has been testing theories and building different rom combinations to try and come up with the best solution possible currently. We've made some amazing progress, and the nostalgic part of me wanted to come back to XDA and not leave you guys in the dark.
We've noticed Custel doing similar things on XDA, and we had already tried a lot of what he was doing. We found that the vogue BT didn't play nice with the rest of the Titan rom components in many situations, yet Custel kept trying. I beleive that some of the devs in our group tried to contact him, possibly even get him involved, share what we've learned so far (collaborative efforts are the best way to go). I don't know exactly what happened after that, and I didn't ask because its not my business. I mentioned him because he's still trying something, where we've had a bit of success. Not that its a race, but it would appear that we got there first using another method. I'm sorry that you read that as a "flame" on his part, I didn't mean to disrespect. Just that we we're doing is not what he's doing, and we've tried that route already.
Some of the others in the group of devs warned me not to go posting here. Thought maybe there would be too much animosity. I decided on my own to bring the information here because XDA was always a great source of info in the past, and there's no reason you guys should be left out. Are you trying to make me regret it, as if I'm wasting my time here?
Lazy and cool6324, I'm not forcing you to try this rom. I'm also not "bragging" about what was created. I'm filling you guys in. If you don't want it, that's fine. I won't bother updating.
hey DISHE
bro u dont even owe these guys an explanation, they contribute nothing and take everything. they dont understand whats involved and quick to criticize anything they dont agree with.
it appears to me that they think they are all that and a bag of chips/ but if the DEVs of these fixes decided not to share, i bet they would keep there mouth shut real quick/
bottom line bro, dont bother posting any more responses to these idiots / look at the end of the "
Hard-SPL - or how to not brick your PDA ever again" post and u will see what these guys are like on this forum, calling each other names and etc just like they r doing now.
i c u at ppcgeeks
Dishe said:
Wow, I've heard of people venting on forums, but this is rediculous. Did you all have really bad days or something?
Look, there's a lot going on that doesn't take place on this forum. I used to be a big XDA-dev's fan, but unfortunatley I've found that there just isn't enough research and development for our particular device going on here, so I started broadening my horizons.
Maybe I didn't make it clear in the first post, but I didn't make this rom.
At least, not by myself. I worked with a team of people from other boards and we formed a group that has been testing theories and building different rom combinations to try and come up with the best solution possible currently. We've made some amazing progress, and the nostalgic part of me wanted to come back to XDA and not leave you guys in the dark.
We've noticed Custel doing similar things on XDA, and we had already tried a lot of what he was doing. We found that the vogue BT didn't play nice with the rest of the Titan rom components in many situations, yet Custel kept trying. I beleive that some of the devs in our group tried to contact him, possibly even get him involved, share what we've learned so far (collaborative efforts are the best way to go). I don't know exactly what happened after that, and I didn't ask because its not my business. I mentioned him because he's still trying something, where we've had a bit of success. Not that its a race, but it would appear that we got there first using another method. I'm sorry that you read that as a "flame" on his part, I didn't mean to disrespect. Just that we we're doing is not what he's doing, and we've tried that route already.
Some of the others in the group of devs warned me not to go posting here. Thought maybe there would be too much animosity. I decided on my own to bring the information here because XDA was always a great source of info in the past, and there's no reason you guys should be left out. Are you trying to make me regret it, as if I'm wasting my time here?
Lazy and cool6324, I'm not forcing you to try this rom. I'm also not "bragging" about what was created. I'm filling you guys in. If you don't want it, that's fine. I won't bother updating.
Click to expand...
Click to collapse
Where was I supposedly contacted?
dishe don't even trip! The folks *****ing are the ones using the Roms also. Take their comments with a grain of salt....F**K EM!!!! Don't waste your time on these idiots. Others apperciate the work you do to make our Moguls useful.
to step: shut ur ass kissing d!ck sucking ***** depriving n a **** hole that you called a mouth! I dont even use BT, yeah its nice to have clean/custom rom to rig my phone. But a stock is fine with me. Just tired of people kissing dev's asses geeze....get them stick out of ur ass....
ps. i never did dish at dishe's rom nor either ***** at it....it was his tactics of bashing on people posts...so get it right...
lazee said:
to step: shut ur ass kissing d!ck sucking ***** depriving n a **** hole that you called a mouth! I dont even use BT, yeah its nice to have clean/custom rom to rig my phone. But a stock is fine with me. Just tired of people kissing dev's asses geeze....get them stick out of ur ass....
ps. i never did dish at dishe's rom nor either ***** at it....it was his tactics of bashing on people posts...so get it right...
Click to expand...
Click to collapse
LMAO...such childish folks here....I'm gonna just LMAO!! at u...so sad
Lazee,
its not about kissing ass. Its about appreciation for what these guys do (AND FOR FREE they do it!!!!) they rarely ask anything of the rest of us, if anything at all. Because of the fact that they do give up alot of free time, which they could be doing something else, to help out alot people they dont even know, i have a certain amount of respect for that alone, regardless if they might seem arrogant. the truth is that they really do care about people or they wouldnt even share what they do! theres no law that says that they have to share anything with us/ sometimes its easy for us to forget this and take it all for granit/ lets just call a truce and stop with the name callin and etc and try to maintain a respectible forum ok.
PEACE!!! come on guys we are all in this together
Oh and by the way Custel, u rock bro, do what it is u do and dont stop!! dishe luvs ya nothing personal, i dont want to speak for him but i get the feeling that things might have came out wrong when he was responding to the "lazee's post and was just a lil fluddered.
I hope this thread does not get me booted off however ... What is the point of this ROM? It has been months and months and many other excellent ROMs are on the board and have been updated continuously with the latest goodies. Da_G and NRG deliver excellent ROMs all the time and yet the REP has yet to release one iteration. I vaguely recall before the thread was locked and purged, that this ROM will still be released at 6.1 although with the current timeline, maybe it will ultimately be released with 7.0. Just a question from a curious reader.
What is the purpose of this ROM? Well maybe just the diversity. So that you dont have to choose between Da_G and NRG only. If you like one of these, then use them. Others who have stayed with the Elite team from RC1 will surely flash RC5 just to see whats new and enjoy the style in which the ROM is created.
I dont quite understand why that particular rom gets stickied anyway but who am I to question the staff's judgement =x
X2D said:
I dont quite understand why that particular rom gets stickied anyway but who am I to question the staff's judgement =x
Click to expand...
Click to collapse
it is pretty annoying, and rather elitist. Why do they think their rom deserves top priority attention? Don't get me wrong, elite RC3 was my first venture into flashing. But from what i've seen, the roms are well out of date compared to any of the others which see frequent updates.
Discussed, re-discussed and re-re-re-re.
Elite's team provided us with the HSPL, it was part of the Touch Pro Elite Project. Without HSPL, no ROM flashing, nothing.
Also they're work got slowed down by some personal issues for two of the members.
I personally stopped using Elite's ROM at around RC3. I also don't see whats the big deal abut it being stickied.
Thread will get closed soon, hopes this answer some questions.
Elite RC1 was my first ROM, currently chrome is my favorite, But I always prefer to have multiple options, stickied or not, keep up the good work!
I do think it's odd that there are now four and presumably five 'Release Candidates', as if what I've already installed hasn't been released. I'm not sure what happens when the team pick one to 'release'? Similarly, it's odd that a thread was setup to release a release candidate 10 days ago, but nothing has materialised and the thread is locked. Why not setup up the thread when the ROM is ready to be downloaded??
To be honest i dont understand what is the problem you see guys. Its just a forum topic. Stored somewhere on a disk drive, taking few Kilobytes of storage. Once again, if you dont want to flash any of the RCs, dont do it. Yes, its stickied, maybe other ROMs should be stickied as well, that wont probably change as soon. So just ignore the threads, if you dont wait for RC5 or dislike the Project as whole.
Again???
How often will this discussion surface?
Does someone have the idea that this is a democratic propoganda site and that the multitude of users determine whats on the menu?
No,.. it's the guys that have the possibility to make a thread sticky who determine this.
They run the show , like it or not.
Of course, in the effect they ignore all the good work done by others!
I take it as it comes. Elite project is not bringing me what I like. I like and use other ROM's instead. No need to nag about it.
Let's stick to the fact that everyone who is contributing to this site,... is in fact contributing! And thats what it's all about!
Haspels said:
How often will this discussion surface?
Does someone have the idea that this is a democratic propoganda site and that the multitude of users determine whats on the menu?
No,.. it's the guys that have the possibility to make a thread sticky who determine this.
They run the show , like it or not.
Of course, in the effect they ignore all the good work done by others!
Click to expand...
Click to collapse
I do not agree with that statement one bit. First of all, you have to earn the moderator status. This status is given to people, who help and contribute the most to the community. Secondly, hardspl for Touch Pro was developed by a member of the Elite team. It is only thanks to this SW that we can flash our devices with any ROM we wish (it doesn't have to be Elite ROM). So there is definatelly a democracy here and the people behind Elite ROM have a great deal to do with it. If what you state were true and the the guys running this forum would really want to "ignore all the good work done by others", they would have had to act exactly the opposite way.
Who cares? If you're not a cook, it shouldn't bother you. Since this is THE place to get a good ROM, it shouldn't matter. Scroll past it and forget it... It should be mentioned that if you go through any of the RC# threads, it's discussed there. Search and find the answer, but I believe it's been mentioned here already...
Thread not related to ROM development and is starting to turn into a flame war.
P.S. If you have a problem with the actions of moderators either take it up with them in Private Message, or speak to the site administrator. Please don't air your dirty laundry in public.
Let's keep the focus on what's important - hacking phones to get the best out of them, and most inportantly, having fun .
Dave
I would like to start learning how to put roms together. I would like to start with developing a 2.2 rom compiled from galaxy s I900 source. Is there anyone here that can point me in the direction of a good tutorial on how to start? I have been using other peoples work for like a year and a half and would really like to create rather than use. I am a total noob when it comes to developing so any help would be great. thx
Go here;
http://forum.xda-developers.com/forumdisplay.php?f=613
Read a lot before you ask.
Good luck!
You can't develop a rom using only kernel source.
Sent from my SCH-I500 using XDA App
Its not kernel only. I am not a total moron. It is the 2.2os downloaded from samsung for the galaxy s i9000
yutzyscott said:
Its not kernel only. I am not a total moron. It is the 2.2os downloaded from samsung for the galaxy s i9000
Click to expand...
Click to collapse
All I have to say is good luck with that.
fallingup said:
All I have to say is good luck with that.
Click to expand...
Click to collapse
In all seriousness do you stay apprised in any way shape or form of android related news our just enjoy smearing the forums with your illinformed ramblings and negativity? Speak of what you know and don't be so eager to dismiss anyone with the fortitude to increase their own knowledge base on an operating system such as this when its these people who we all depend on to better our experience with said operating system. As it is these people for whom google turns to when it comes to ideas on how to better their future stock releases. Thank you for the vote of confidence.
Sent from my SCH-I500 using XDA App
You do realize fallingup has written more android code than your phone can hold?
The reason they seem testy is they(actual developers) have been spending all their free time trying to get Samsungs crappy code to compile, and every couple of hours some one asks for an easy how to guide for porting Froyo.
Spend some time reading the forums. Find out what is already being done, then learn the basics of rom development. THEN, ask intelligent questions on how help develop Froyo for our phones.
Asking for an easy way to cook roms is the equivalent of the kid in the back seat asking "are we there yet" every 30 seconds. If you really want to learn how to cook roms, try a couple easy ones with the kitchen I linked to, then learn how to work on roms without the kitchen. Then work on Froyo. There is no easy way.
I didn't ask for an easy how to thinking that I could have it done by tomorrow or even that I could figure it out at all. I simply asked for a starting point and stated in the OP that I am a know nothing when it comes to developing. As far as my last post I meant no disrespect to fallingup in fact it was my mistake to quote his post. I actually intended on quoting jt1134 so, to fallingup, I have used your stuff many times and have nothing but respect for what you do. I apologize for the misquote. I in no way think myself to be super genius to the 10th power nor do I believe that I can actually do anything worth while with this code. I'm just bored and want to learn. I'm also an Android addict.
P.S. Thank you for the link. Also you'll notice in my last post now that you know of my misquote, that I am actually 100% behind people like fallingup. I would never knowingly give a verbal bashing like that to him.(god I feel like **** now)
You meant to quote ME? Wow.
In all seriousness, and no disrespect intended, I'll explain a few things.
The code Samsung provides is NOT the full OS. Not even close. It's the kernel, plus a few android packages. In most cases, the android packages are EXACT copies of the code that has been available from Google for months, and in other cases has one line changes referencing a Makefile that doesn't exist. This is no way gets us any closer to a 2.2 rom other than the kernel. What we REALLY need is a working 2.2 ota build or leaked package to move forward any faster. That is MUCH more important than the garbage that Samsung has been releasing to us.
If you are a noob to development, then GOOD LUCK. If you are an advanced developer with intimate knowledge of android, then GOOD LUCK. There are quite a few of us working on aosp ports to the SGS phone series, and so far it has not been completed for a SINGLE device.
There are no guides that will explain exactly what is needed to accomplish this goal. There is no one who is going to hold anyone else's hands through it. Hacking is a meritocracy, meaning you'll get help with advanced topics when you show you have done your research, put effort into resolving the issue on your own, and ask intelligent and informed questions that give exact details of the situation.
If you would like to continue to show a poor attitude, then go for it on your own. Wait for us to release a working rom. If you would like to actually learn and invest some time in moving forward, the GO FOR IT, you are VERY WELCOME to do so. Read the porting guides written by google, try some stuff out, and come over to IRC and get your hack on.
I'm tired. I'm generally a nice guy, sorry!
jt1134 said:
You meant to quote ME? Wow.
In all seriousness, and no disrespect intended, I'll explain a few things.
The code Samsung provides is NOT the full OS. Not even close. It's the kernel, plus a few android packages. In most cases, the android packages are EXACT copies of the code that has been available from Google for months, and in other cases has one line changes referencing a Makefile that doesn't exist. This is no way gets us any closer to a 2.2 rom other than the kernel. What we REALLY need is a working 2.2 ota build or leaked package to move forward any faster. That is MUCH more important than the garbage that Samsung has been releasing to us.
If you are a noob to development, then GOOD LUCK. If you are an advanced developer with intimate knowledge of android, then GOOD LUCK. There are quite a few of us working on aosp ports to the SGS phone series, and so far it has not been completed for a SINGLE device.
There are no guides that will explain exactly what is needed to accomplish this goal. There is no one who is going to hold anyone else's hands through it. Hacking is a meritocracy, meaning you'll get help with advanced topics when you show you have done your research, put effort into resolving the issue on your own, and ask intelligent and informed questions that give exact details of the situation.
If you would like to continue to show a poor attitude, then go for it on your own. Wait for us to release a working rom. If you would like to actually learn and invest some time in moving forward, the GO FOR IT, you are VERY WELCOME to do so. Read the porting guides written by google, try some stuff out, and come over to IRC and get your hack on.
Click to expand...
Click to collapse
Now I have the right person quoted. Did you even read my post??? Let me repeat a key part so that you can understand and maybe you can stop battering the new guy.
"I didn't ask for an easy how to thinking that I could have it done by tomorrow or even that I could figure it out at all. I simply asked for a starting point and stated in the OP that I am a know nothing when it comes to developing."
I have admitted to my know nothingness. I simply want to learn. You could respond with something such as Galaxy S 2.2 is not a good place to start the learning process. Or you could have left it alone entirely and just thought that the link posted by "sgtmack" was sufficient enough. After all it did answer the exact question I asked. You might know a lot more about code and code writing than me but you have to admit, "your kind of an arrogant ass!" Now I would like to end this banter by allowing you to respond in whatever way you deem necessary. I myself will give this no further thought as I would like to move on now. That and I believe I have made myself look bad enough now.
As for fallingup and sgtmack, thanks for the hard work and helpful advice.
yutzyscott, do you not realize that jt and dirrk are the ones that got us the voodoo kernel? do you know they are the ones that got the kernel booting in the first place using samsung's ****ty source code? without jt, there would be nothing to build a rom around. wtf do you mean ill-informed when jt probably knows more than most people about developing for this phone? pay some ****ing respect for people that deserve it.
Yeah I do but, when this whole thing started I did not read who the post was by but, rather I just read the post. While I appreciate his work and am actually using it, my pride was hurt and its hard to interpret someones tone on a forum. I was under the impression in the beginning of all this that it would be known that I downloaded the 2.2 ota pushed to the original galaxy s and not the source they have been working with and making leaps and bounds with despite the road blocks. I was interested in learning how to port it (the ota I mean) rather than just sitting on my hands waiting to use anothers work. Chances are that I would never even come close to understanding what I was looking at but, I had to try. Now I'm sorry I asked. I quit...I was wrong, sorry! Leaving it to the experts. I'll go back to helping people with simple basic problems on droidforums.net and continue being an expert on using the real experts work.
This doesn't need to be turned into a flame thread. So here's my advice: join us on irc.freenode.net #samsung-fascinate and ask questions there. learn how to build a kernel, and maybe try to find out how exactly to port roms from other devices. Its a tough business, especially when we don't even get working kernel source from the manufacturer.
There are a ton of people that are working on the galaxy s phones, trying to get AOSP and the like on them. These phones are quite different than any other android phones, just with the way that the hardware / partitions are, so there is a lot to work through and document. Once one of the SGS phones is running aosp, im sure the others wont be too far behind. I wouldn't bother porting another crappy samsung rom, cause it will still have a lot of the crap that we are trying to get rid of by running aosp.
Thanks. And to jt, im sorry for being an argumentative ****. Thanks for all your hard work and despite the fact that there are many having issues with voodoo I am one of the many who it is working beautifully for.
Sent from my SCH-I500 using XDA App
yutzyscott said:
Thanks. And to jt, im sorry for being an argumentative ****. Thanks for all your hard work and despite the fact that there are many having issues with voodoo I am one of the many who it is working beautifully for.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Hey no hard feelings man. This was the first thing I saw after waking up today so I got rubbed the wrong way. Apologies. Feel free to catch me on IRC and I'm always happy to answer any questions relating to compiling stuff for our phones
jt1134 said:
Hey no hard feelings man. This was the first thing I saw after waking up today so I got rubbed the wrong way. Apologies. Feel free to catch me on IRC and I'm always happy to answer any questions relating to compiling stuff for our phones
Click to expand...
Click to collapse
Me too. I was drunk last night and after three hours of sleep I started responding on this thread.
Sent from my SCH-I500 using XDA App
yutzyscott said:
Me too. I was drunk last night and after three hours of sleep I started responding on this thread.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Thats always a good excuse
this was an entertaining thread lol.. misunderstandings is one of the biggest downfalls of online conversation.
Not meant to be offensive. Just funny. http://www.geekologie.com/2010/10/a_day_in_the_life_of_internet.php
Sent from my SCH-I500 using XDA App
First, and foremost, hello. I am new here, and I'm glad to be a part of the forum. Secondly, I'd like to apologize if I am posting this in the wrong section.
The topic I'd like to ask you a few questions about today is ROM Flashing, and the steps I should be taking to stay safe. I originally started playing around with Android devices around a year ago, but I recently started to delve deeper. I am the proud owner of an AT&T ZTE Z998 Mustang, and I have rooted it successfully. While in the process of rooting, I saw all of the warnings of how I should do a NANDROID backup, so that was my first instinct. I tried installing Clockworkmod, but to my dismay, they did not have an official version for my phone. I did happen to get lucky and find a version someone ported on their own. I attempted for a whole night before falling prey to error after error, and decided to give up. I went on without any backups, fiddling with my device. Luckily, I did not mess anything up, except for "accidentally" deleting the AT&T startup animation. (Haha.) Tonight, though, I happened to get the urge again, so I made some more attempts. After receiving the same error, I decided to look that error up word for word, and found that I did not have enough room on my Micro SD. I managed to clear enough room, and jumped in joy when I saw that I could delete an app, then restore and have it be back again. It was quite a big accomplishment for me. I've decided that I want to try flashing a custom ROM. The ROM I have chosen is the MIUI ROM. It seems quite popular, and I enjoy the iOS-esq feel of it, as well as its seamless theme changing. The only problem is, there is not an official release for my device. In fact, I have yet to find any ROM with an official release for my device. That is why I am coming to you guys.
My Questions:
Can I use a ROM that has not been specifically made for my device?
Will I still be connected to the AT&T Network?
If so, can I expect errors?
Am I truly safe with this newly acquired backup?
Anything you think I should know?
I'd like to thank you for any help in advance.
BrendonButton said:
First, and foremost, hello. I am new here, and I'm glad to be a part of the forum. Secondly, I'd like to apologize if I am posting this in the wrong section.
The topic I'd like to ask you a few questions about today is ROM Flashing, and the steps I should be taking to stay safe. I originally started playing around with Android devices around a year ago, but I recently started to delve deeper. I am the proud owner of an AT&T ZTE Z998 Mustang, and I have rooted it successfully. While in the process of rooting, I saw all of the warnings of how I should do a NANDROID backup, so that was my first instinct. I tried installing Clockworkmod, but to my dismay, they did not have an official version for my phone. I did happen to get lucky and find a version someone ported on their own. I attempted for a whole night before falling prey to error after error, and decided to give up. I went on without any backups, fiddling with my device. Luckily, I did not mess anything up, except for "accidentally" deleting the AT&T startup animation. (Haha.) Tonight, though, I happened to get the urge again, so I made some more attempts. After receiving the same error, I decided to look that error up word for word, and found that I did not have enough room on my Micro SD. I managed to clear enough room, and jumped in joy when I saw that I could delete an app, then restore and have it be back again. It was quite a big accomplishment for me. I've decided that I want to try flashing a custom ROM. The ROM I have chosen is the MIUI ROM. It seems quite popular, and I enjoy the iOS-esq feel of it, as well as its seamless theme changing. The only problem is, there is not an official release for my device. In fact, I have yet to find any ROM with an official release for my device. That is why I am coming to you guys.
My Questions:
Can I use a ROM that has not been specifically made for my device?
Will I still be connected to the AT&T Network?
If so, can I expect errors?
Am I truly safe with this newly acquired backup?
Anything you think I should know?
I'd like to thank you for any help in advance.
Click to expand...
Click to collapse
Bump.
Hi there. Welcome to the forums!
Unfortunately, the bad thing about phones that aren't very popular in the grand scheme of things means less people have them = less people making stuff for it. Developers often end up picking phones that are going to have more support from the manufacturer and more people will be able to enjoy the fruits of their labors. This of course, is a general rule, and of course there are exceptions, but your phone doesn't seem to be one of them. Companies like ZTE aren't concerned about putting out the source code for phones like this means that it is hard, to almost impossible, to make a really custom rom work correctly due to driver issues among other things.
So to answer the questions:
1) Sometimes, but very dependent on the models, carriers, and which software updates. General rule of thumb is that if it isn't based off the same chipset, it won't have a chance of working. But there are lots of other things to consider to, like radio versions, bootloader status, partition layout, etc. Long story short, there's no easy answer and there are lots of caveats.
2) + 3) See above.
4) You SHOULD be safe if CWM told you that the nandroid was completed successfully, but just like any other software based things, things happen.
Best way to be safe is to be able to reflash the original firmware for the phone back to it, but not even sure if that's an option for you - which goes back to ZTE not giving a $^!* about these cheap little phones for small prepaid companies. They save money by not doing any extra work like providing firmware, updates, source code, etc.
The only forums I know that mess with these kinds of things are:
http://unleashedprepaids.com/forum-1491.html
Not for your phone specifically, but similar ones:
http://androidarea51.com/zte-phones/
So yea, slim pickings.
es0tericcha0s said:
Helpful Info.
Click to expand...
Click to collapse
First, thank you! I was waiting all day. I was a little disappointed with the answer, though. v.v Do you know if there are any ROMS that will work with ANY device? Like even bare minerals versions of AOSP ROMS that have yet to be touched?
Also, I am slowly saving for a 64GB Black Nexus 5, so I shouldn't be stuck but more than a month or more so.
BrendonButton said:
First, thank you! I was waiting all day. I was a little disappointed with the answer, though. v.v Do you know if there are any ROMS that will work with ANY device? Like even bare minerals versions of AOSP ROMS that have yet to be touched?
Also, I am slowly saving for a 64GB Black Nexus 5, so I shouldn't be stuck but more than a month or more so.
Click to expand...
Click to collapse
No, sorry. It's just not possible. Your best hope would be to use the debloated rom in the unleashed prepaids forum and use the Xposed Framework.
http://unleashedprepaids.com/thread-8769.html
http://unleashedprepaids.com/thread-8771.html
http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401
http://repo.xposed.info/module-overview
I have the Nexus 5 (don't think they come in 64 - only 16/32) but it's awesome and there are so many roms that it'll make your head spin. lol
es0tericcha0s said:
No, sorry. It's just not possible. Your best hope would be to use the debloated rom in the unleashed prepaids forum and use the Xposed Framework.
http://unleashedprepaids.com/thread-8769.html
http://unleashedprepaids.com/thread-8771.html
http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401
http://repo.xposed.info/module-overview
I have the Nexus 5 (don't think they come in 64 - only 16/32) but it's awesome and there are so many roms that it'll make your head spin. lol
Click to expand...
Click to collapse
Oops, sorry, yeah, that's what I meant. xD
But, I can not wait for it!
Just some final thoughts and questions:
I do have Xposed installed already, but have yet to look around in it due to the hundreds of modules. Do you have any suggestions about which I should look at for cosmetic needs? I have tried to use Gravitybox, but it force closed upon entry every time I used it, so I deleted it.
I understand that the limitation is very high because of the fact that it is a closed sourced company, but many ZTE Devices are listed to have compatible ROMS, such as MIUI ROM. If I try to use a ROM specified for a different phone, do you know what could happen? I feel that it may not even open, or if it does, it'll have tons of errors and not work upon entry, or even work but have certain things like the camera that will not connect. I'm only worried about high margins of fatal breakage. If it is some silly error that I won't have to "worry" about, I'm okay with fooling around.
If I do try to install a new ROM, but want to go back, will it affect anything on my previous backup? I know backups copy EVERYTHING, but I'd just like to make sure I won't do serious damage.
Lastly, thank you for all the help. It means a ton.
BrendonButton said:
Oops, sorry, yeah, that's what I meant. xD
But, I can not wait for it!
Just some final thoughts and questions:
I do have Xposed installed already, but have yet to look around in it due to the hundreds of modules. Do you have any suggestions about which I should look at for cosmetic needs? I have tried to use Gravitybox, but it force closed upon entry every time I used it, so I deleted it.
I understand that the limitation is very high because of the fact that it is a closed sourced company, but many ZTE Devices are listed to have compatible ROMS, such as MIUI ROM. If I try to use a ROM specified for a different phone, do you know what could happen? I feel that it may not even open, or if it does, it'll have tons of errors and not work upon entry, or even work but have certain things like the camera that will not connect. I'm only worried about high margins of fatal breakage. If it is some silly error that I won't have to "worry" about, I'm okay with fooling around.
If I do try to install a new ROM, but want to go back, will it affect anything on my previous backup? I know backups copy EVERYTHING, but I'd just like to make sure I won't do serious damage.
Lastly, thank you for all the help. It means a ton.
Click to expand...
Click to collapse
Gravity Box wouldn't work because it is for more AOSP based things. As far as theming goes, you can try HK Theme Manager or Ex Themer. For the idea of trying to install a rom for another ZTE phone, well, best case scenario is that it doesn't flash at all. Worst case is that it does flash, and you lose something like your IMEI, baseband, or one or more of your other partitions and all of those are potentially unrecoverable, no matter what kind of backups you have. This wouldn't be one of those, "Oh, shoot, that didn't work, I'll just factory reset or restore my backup and be good to go..." kind of situations.
es0tericcha0s said:
Gravity Box wouldn't work because it is for more AOSP based things. As far as theming goes, you can try HK Theme Manager or Ex Themer. For the idea of trying to install a rom for another ZTE phone, well, best case scenario is that it doesn't flash at all. Worst case is that it does flash, and you lose something like your IMEI, baseband, or one or more of your other partitions and all of those are potentially unrecoverable, no matter what kind of backups you have. This wouldn't be one of those, "Oh, shoot, that didn't work, I'll just factory reset or restore my backup and be good to go..." kind of situations.
Click to expand...
Click to collapse
Oh, wow! Thanks! I'm glad you pointed that out before I tried. So, I should be okay as long as I flash that ROM from the Unleashed Prepaid page? Now I am afraid, but curious.
Also, thank you for the theme modules names, I will kindly note them.
Should be fine. It's 95% stock and I'm sure they only had one version of android for the phone so should be pretty close to what you have now. Benefits would be the unsecured boot.img which is easier for root and other things to stick, init.d which allows you to run scripts (everything from being able to mount a partition of an SD card to use for extra space for apps to memory management stuff like V6 Supercharger), and a bit easier to theme and debloat.
es0tericcha0s said:
Should be fine. It's 95% stock and I'm sure they only had one version of android for the phone so should be pretty close to what you have now. Benefits would be the unsecured boot.img which is easier for root and other things to stick, init.d which allows you to run scripts (everything from being able to mount a partition of an SD card to use for extra space for apps to memory management stuff like V6 Supercharger), and a bit easier to theme and debloat.
Click to expand...
Click to collapse
Thank you.
I'll look into it tonight. I will try and tell about what happens tomorrow-ish.
Cool. Good luck.
Theres something that was pointed out to me by a new friend, that I had to vent about.. so HERE IT IS!!1
Why are some people too good to hang out in their threads and answer questions about the builds they post???
It seems to me that it builds credibility, to help the people using your build, so why not hang out and answer questions, address issues, help finding solutions, offer advice... BE HUMAN
Sure its great that new builds are being pushed out constantly... BUT IF YOURE NOT TALKING TO THE PEOPLE RUNNING THE CURRENT ONE AND EXPERIENCING PROBLEMS WHAT GOOD IS IT????
Step down from the clouds, and walk barefoot on the grass with the rest of us.. its cool and refreshing on your feet
WOW Man..
pitbull8265 said:
Theres something that was pointed out to me by a new friend, that I had to vent about.. so HERE IT IS!!1
Why are some people too good to hang out in their threads and answer questions about the builds they post???
It seems to me that it builds credibility, to help the people using your build, so why not hang out and answer questions, address issues, help finding solutions, offer advice... BE HUMAN
Sure its great that new builds are being pushed out constantly... BUT IF YOURE NOT TALKING TO THE PEOPLE RUNNING THE CURRENT ONE AND EXPERIENCING PROBLEMS WHAT GOOD IS IT????
Step down from the clouds, and walk barefoot on the grass with the rest of us.. its cool and refreshing on your feet
Click to expand...
Click to collapse
Could not have said it better.... You hit the nail right on the head.. People respect those who back their work with support:good::good::good:
This DOES seem to be in SHORT reserve.. WELL STATED
Impressive
I have noticed this too.. Its like these people are too GOOD for Q&A and sometimes even respond to questions like they are PETTY and an inconvenience.. There ARE some who DO help, and those people deserve to know they are appreciated.. You in particular, have helped me a ton, so thanks.. Maybe you'll start a movement, and more people will start doing their part to help their followers...
+1
There is a SERIOUS shortage of helpers and an overage of shovelers
All these builds keep coming, and still the same problems on the one they put out before with a different NAME for the ROM.. Its like they change the name and recycled it..
I read through threads now, and if the OP doesn't hang out and help their users, I wont use their builds anymore.
Couldn't agree more!! Nicely said too
Be proud of your work.. Stick around and make sure people can..ya know, enjoy it too..
It's quality not quantity that matters. Stepping on other teams and developers to rush something out just to say "FIRST" will get you no where.. So while timely updates are important, if that's the only thing you post in your own thread.. "New build is up" when there's been 10 pages of people asking questions... I'll never support you, both publicly or financially.
I understand new enthusiast can be quite frustrating or maybe you just aren't a people type of person.. team up with someone that is... pass the q&a on to them, but do fricking something, people want support for YOUR roms and if you put out 20..that means all 20.
Exactly, how dare these developers not spend any time in the forums answering the same useless non-informative questions over and over. How dare they spend countless hours building a ROMs for free and then share it for others to use. How dare they spend time with their families and go to their actual job and have a life. How dare they….. (/sarcasm)
mapatton82 said:
Exactly, how dare these developers not spend any time in the forums answering the same useless non-informative questions over and over. How dare they spend countless hours building a ROMs for free and then share it for others to use. How dare they spend time with their families and go to their actual job and have a life. How dare they….. (/sarcasm)
Click to expand...
Click to collapse
Yea, I'm somewhere between this and the op. They shouldn't be 100% absent, but on the same note, some consideration for the above quote is in order too.
While were venting, its possible the devs haven't figured out how to fix some of these issues, but it doesn't do a dam bit of good for 50 people to complain about the same thing and no one is posting logcats. So don't complain about things not getting fixed, if your not attaching logs to every post about issues.
Just my 2c, add 97c more and go buy a cheeseburger.
Sent from my G3, Unlocked by Team Codefire
mapatton82 said:
Exactly, how dare these developers not spend any time in the forums answering the same useless non-informative questions over and over. How dare they spend countless hours building a ROMs for free and then share it for others to use. How dare they spend time with their families and go to their actual job and have a life. How dare they….. (/sarcasm)
Click to expand...
Click to collapse
Then why put out 20 instead of 1 that they can handle is the point!!
Variety is the spice of life. I'd rather have 20 that will get fixed eventually than just 1 that works perfectly. If they are all too similar for you then just move on to another one, build your own, or just wait for fully featured lollipop which will be here soon enough. If a thread is maintained or not - I'm just happy to have a thread. A couple devs have walked away already and it'd suck if more left. Just be grateful for what we've got and be patient.
Kris Nelson said:
Then why put out 20 instead of 1 that they can handle is the point!!
Click to expand...
Click to collapse
The same person is not releasing 20 different versions. Also, most are all based off of the AOSP core source, but each dev might add their own touch/flare to it. But, since each one is based off of AOSP, then more than likely, they will all have the same issues, unless the dev has made some changes.
I'd rather have a lot of choices than none. Believe me, when there is NO dev support (that is, a lot of ROMs being release), then you get even MORE whining of "Why isn't there any ROMs/dev support for this?"
Maybe you're not a dev, but I am (not for ROMs but that is my full-time job). Development takes a lot of time. I do it at work and to do it at home as well, especially for something that is free, takes a lot of time and dedication. Especially, ROM development is NOT an easy task. Rebuilding ROMs takes at least 90 minutes or more, depending on the speed of your machine, the size of the source code, etc. Heck, I've pulled down the git for CM12 and it's 12gb in size (source code only, not compiled) and it took hours to download over my high-speed internet connection at home.
I can understand wanting support if you PAID for it, but this is free, people. Free. They don't ask for anything in return monetarily, and yet, we see people demanding support as if they paid for it. You get what you pay for, and in this case, it's free. But I feel the support most devs give is very good, considering it's free. Also, for things like CM, it's usually not just one dev, but several who have responsibilities for different parts of the Android code base. So, just because one guy posts about it, doesn't mean he's the only dev on it. He might be sending your findings back to the other devs.
Also, you DON'T have to flash these custom ROMs. They all have disclaimers that the dev is not responsible for any damages that may occur to your phone. They don't guarantee support, but it's there for you to use. However, who is to say they aren't monitoring the forums? Just because they don't respond, doesn't mean they aren't looking into the issues you report.
Yes, I understand how you want a response from them, but in the end, it is your choice whether you want to flash or not. They didn't twist your arm to do it.
Keep posting your defects. Most devs, the good ones, do monitor the forums and take note of the issues. However, they know about other major issues that they are probably trying to work on. Again, for most, it is done in their spare time.
I myself would like to build and release ROMs, but right now, I don't have the time. it's not just "make a change, compile, release". There is a lot of researching, debugging, etc that must go on. Those that are programmers understand this. And, once you fix a bug, you don't just go and release it (under normal circumstances). You have to go through a complete testing cycle, retesting previous tests along with any new tests to ensure you didn't break something else. It's not that simple.
However, with these free releases, WE are the testers. WE are the ones that report back the issues so they can be addressed. Post them here, or even some devs have Twitter pages where you can post defects. Not all, but some.
In the end, be thankful you have so many choices. Yes, it may seem as if they are all the same, and in some cases they are and some are from people who just want to say "look I released a ROM" and then you never hear from them again. But, in the case of XDA, to post about a ROM in the dev forum, I believe you have to be an identified developer, so they do have to go through some vetting process. So, more than likely, they are legit developers, not a fly-by-night person.
Just wanted to get that off my chest. I understand what people feel, but you have to understand, this is not an easy thing to do. Maybe a lot of you understand that, but I find that a lot don't. Or, they say they understand, when they really don't. They just "think" they understand.
Wow. Off the soapbox. It just burns me as a developer when I see things like this. Yes, I understand where you are coming from, but sometimes, I think you need to hear it from the other side as well.
Ciao!
If you're a good parent, when you bring a child into this world, you raise it, and nurture it... creating it is not enough...
noun
1.
the act or process of developing; growth; progress:
iBolski said:
The same person is not releasing 20 different versions. Also, most are all based off of the AOSP core source, but each dev might add their own touch/flare to it. But, since each one is based off of AOSP, then more than likely, they will all have the same issues, unless the dev has made some changes.
I'd rather have a lot of choices than none. Believe me, when there is NO dev support (that is, a lot of ROMs being release), then you get even MORE whining of "Why isn't there any ROMs/dev support for this?"
Maybe you're not a dev, but I am (not for ROMs but that is my full-time job). Development takes a lot of time. I do it at work and to do it at home as well, especially for something that is free, takes a lot of time and dedication. Especially, ROM development is NOT an easy task. Rebuilding ROMs takes at least 90 minutes or more, depending on the speed of your machine, the size of the source code, etc. Heck, I've pulled down the git for CM12 and it's 12gb in size (source code only, not compiled) and it took hours to download over my high-speed internet connection at home.
I can understand wanting support if you PAID for it, but this is free, people. Free. They don't ask for anything in return monetarily, and yet, we see people demanding support as if they paid for it. You get what you pay for, and in this case, it's free. But I feel the support most devs give is very good, considering it's free. Also, for things like CM, it's usually not just one dev, but several who have responsibilities for different parts of the Android code base. So, just because one guy posts about it, doesn't mean he's the only dev on it. He might be sending your findings back to the other devs.
Also, you DON'T have to flash these custom ROMs. They all have disclaimers that the dev is not responsible for any damages that may occur to your phone. They don't guarantee support, but it's there for you to use. However, who is to say they aren't monitoring the forums? Just because they don't respond, doesn't mean they aren't looking into the issues you report.
Yes, I understand how you want a response from them, but in the end, it is your choice whether you want to flash or not. They didn't twist your arm to do it.
Keep posting your defects. Most devs, the good ones, do monitor the forums and take note of the issues. However, they know about other major issues that they are probably trying to work on. Again, for most, it is done in their spare time.
I myself would like to build and release ROMs, but right now, I don't have the time. it's not just "make a change, compile, release". There is a lot of researching, debugging, etc that must go on. Those that are programmers understand this. And, once you fix a bug, you don't just go and release it (under normal circumstances). You have to go through a complete testing cycle, retesting previous tests along with any new tests to ensure you didn't break something else. It's not that simple.
However, with these free releases, WE are the testers. WE are the ones that report back the issues so they can be addressed. Post them here, or even some devs have Twitter pages where you can post defects. Not all, but some.
In the end, be thankful you have so many choices. Yes, it may seem as if they are all the same, and in some cases they are and some are from people who just want to say "look I released a ROM" and then you never hear from them again. But, in the case of XDA, to post about a ROM in the dev forum, I believe you have to be an identified developer, so they do have to go through some vetting process. So, more than likely, they are legit developers, not a fly-by-night person.
Just wanted to get that off my chest. I understand what people feel, but you have to understand, this is not an easy thing to do. Maybe a lot of you understand that, but I find that a lot don't. Or, they say they understand, when they really don't. They just "think" they understand.
Wow. Off the soapbox. It just burns me as a developer when I see things like this. Yes, I understand where you are coming from, but sometimes, I think you need to hear it from the other side as well.
Ciao!
Click to expand...
Click to collapse
Thank you.. Just to correct you though.. There ARE the same persons that are putting out 20 different versions (1 developer. releasing 20 different roms.) That was just the point i was making..
I do personally research before i ever flash a rom or anything..and trust me i donate!! LOL
Kris Nelson said:
Thank you.. Just to correct you though.. There ARE the same persons that are putting out 20 different versions (1 developer. releasing 20 different roms.) That was just the point i was making..
I do personally research before i ever flash a rom or anything..and trust me i donate!! LOL
Click to expand...
Click to collapse
I see who you are talking about. If you read the OP, at the bottom, he gives thanks to the devs on these ROMs. I don't think he's a developer at all. At least, his profile doesn't say so. I think he just finds all these ROMs and posts links to them. I could be wrong, and I apologize if I am if that person is reading this thread, but I don't see where the OP of the 5+ ROM threads is the actual developer for them. It's almost like he does the "announcing" for the devs of those ROMs.
And since it does appear that you do not have to be a developer to post in the standard DEV forum, then that makes even more sense.
I do know that in another forum I frequented a lot, you were given developer status and only developers could create new threads in the DEV/ROM forum. That was to prevent a lot of "spam" postings of ROMs.
Makes me wonder if that's what is happening here.
iBolski said:
I see who you are talking about. If you read the OP, at the bottom, he gives thanks to the devs on these ROMs. I don't think he's a developer at all. At least, his profile doesn't say so. I think he just finds all these ROMs and posts links to them. I could be wrong, and I apologize if I am if that person is reading this thread, but I don't see where the OP of the 5+ ROM threads is the actual developer for them. It's almost like he does the "announcing" for the devs of those ROMs.
Click to expand...
Click to collapse
I wish you were correct but nope, he is the builder and maintainer. Trust me many more than 5+ when you include other carriers as well.. But not just the one, others have started as well... It's very frustrating that after 1 week, several messages of a very specific problem (not mine just someone i was helping) on different sites where they are posted.. I have to track down someone that i know can help but has NOTHING to do with any of these roms...and gets zippy cash.. Though he should..lol
Anyway, i truly value great developers and have learned who to support and who not to. I like to help people so the developers can build awesome stuff and its my way of keeping the simple crap of your plate so you can do just that..but when i can't even find the answer, the developer should be available.
Just saw your edit.. Yes i think that is happening too. I was always under the assumption that builders/maintainers did so for the actual devise and carriers they use.. I guess that's no longer the case.
Oadam11 is a builder of various roms for our G3's from source repositories available for anyone to build from, and anyone to commit to. He may or may not be doing any commits/merge requests - and even if he did those contributions might not be accepted into the various G3 forks.
In any case, he might not be in a position to contribute to feature requests or bug fixes. He might not be running his own builds of all these roms, past checking to see if they will boot and more or less work.
Say Team Vanir does a fork of their work for the G3, an official one. Ok, then you would ask for support from members of Team Vanir, sure, though you might not get much, depending on a lot of factors (including your attitude...) Then consider the possibility that someone just builds something like Commotio from publicly available sources, with just enough tweaks from somewhere to get it to compile and run, unofficially, on one or more G3 variants. I suspect that is where oadam11 is coming from. He doesn't create the roms, he builds them for G3's. He watches the repositories for each rom he has built for us, and when he sees that rom's devs have checked in and merged useful updates, then he rebuilds for us when he has time. Builds take a while. Then he makes them available for us users to download and install them, after some degree of testing.
The point is that he is in no way responsible for supporting the builds he produces of these team's work. It would be impossible for him to anyway. I am sure he gets permission and some degree of cooperation from any team project he builds from, but he is NOT a team member, or major contributor, for all of them. He is a noble builder and distributor, and you should expect nothing more from him than What he is already providing.
If you want to get a problem or new feature dealt with on any given rom, you must deal with the team's source contributers by raising issues on their gerrit or maybe working on an outstanding and team-prioritized bug as a contributor.
Sent from my VS985 4G using Tapatalk
Thank you..you actually confirmed the point I was making. However, is the average person going to know all this? Of course not...should they do their research prior, of course but they don't... I see good teams being hurt by this as well.. Vanir just had an issue the other day.. Something is being lost in translation and by no means was i only referring to Adam.
I understand. It is interesting that in G+ just a little why ago someone asked David Kessler of Team Vanir who was their maintainer of the G3 Vanir and he replied that they don't have one.
There was also discussion about someone providing support, like answering questions. The idea of supporting a clueless user who had tried to flash TouchWiz onto a Vanir device, by beating the user over the head with an iPhone6+ was suggested. The devs have no patience with such users, generally.
That said, Holy Angel seems exceptional.
Sent from my VS985 4G using Tapatalk
The problem I have, is that when a person POSTS a Rom, and are the OP, they need to support what they post, and help the people posting questions in the thread, or BOW OUT!!! There are people posting and dumping... DONT Post a ROM if you're not willing or able to help the team you are Posting links to... Dont post it and then say "Any problems, contact THEM"
THAT PERSON mentioned, has a lot of them, all as OP, none supported other than.."New build up"
Raising the age limit for COPPA
The amount of entitlement exhibited in this thread is phenomenal. Yes, by all means don't use a build if the developer (who has actually done some REAL WORK) won't support you to your liking.
That will really teach those mean developers a lesson.
Don't forget to complain about the slow speeds of free downloads as well.
It's also a good idea to stop using a build if the developer won't add features you want, and soon, too.
DeanGibson said:
The amount of entitlement exhibited in this thread is phenomenal. Yes, by all means don't use a build if the developer (who has actually done some REAL WORK) won't support you to his/her liking.
That will really teach those mean developers a lesson.
Don't forget to complain about the slow speeds of free downloads as well.
It's also a good idea to stop using a build if the developer won't add features you want, and soon, too.
Click to expand...
Click to collapse
Just because you want a feature, doesn't mean it's a good feature to add. If you did that, you would end up with something that could eventually become impossible to maintain.
There are SO many bugs right now in the AOSP code that these devs are trying to fix to make it work on this phone. I would rather those get fixed first.
And, do you think you are the only one to ask for features?
I'm a developer, not for android, but I write code for a living. And what you are asking for is what we call "scope creep". We have to weed out the "must haves" with the "wants". Must haves are the things that they user must have in order to perform their job. This is usually adding functionality that isn't there currently that is needed to complete their job. The "wants" are "I would like to have the ability to clear out all background apps with a single button or swipe". That is NOT needed on this phone, but it's a nice "to have" option, but it doesn't affect the overall performance of the OS itself. Yes, you might say it does because you can clear out the background apps, but in reality, those apps are NOT running. I don't want to get into the specifics of android app management, but those apps you see in the "recent apps" history are NOT running. They are suspended and not taking up ANY CPU cycles, what-so-ever. If they happen to be, then it's a poorly written app, and it means the dev knowingly circumvented the Android OS app management process which is a big no-no. In that case, you should go back to the dev of the app and demand they fix that.
But, you are free not to install the ROM. That's fine and that's your choice, but it just irks me when I see people make complaints like this who probably have no idea what the software development life cycle is all about. To me, fixing bugs right now is the main issue, not adding pretty enhancements to the OS.
And who's to say they aren't working on what you ask, especially if you ask for fixes to major issues (such as battery life, radio, etc)?
Remember, these are UNOFFICIAL releases. They are based off of AOSP source which is pretty much device-agnostic except when it comes to Nexus devices since those are Google devices and therefore, the AOSP source is built for those type of devices.
Android is completely different from iOS. iOS is built for a set of hardware that doesn't have much variance like Android does. Hence, that is why Apple controls both the software AND the hardware of iPhones. It means less fragmentation across devices, but it also means, they decide what is best and you have no way of getting the source.
Google releases the source for Android so you CAN have these custom ROMs built. But, because one Android device has a different hardware configuration from another (CPU and GPU's being the biggest ones), then anything that can take advantage of the hardware architecture for a particular phone means having to change the AOSP source to use any of those "advantages" from that hardware. Which then means, that source no longer works on other phones, only for the phone they modified it for.
So, give the devs some slack, please. They are working hard on it and it's not one dev. If it were, then give the guy even MORE slack. The source for Android is over 12gb along. That is where it's not even compiled. And, compiling the android source generally takes about 90 minutes. So, each "fix" they do requires recompiling (90 minutes) and then testing.
Then, more than likely, the "fix" either didn't work or it possibly broke something else. That means, going back, determining the issue, fixing it, recompiling (wait another 90 minutes) and test again.
That all takes time, people. We developers are NOT magicians, even though it might seem like it.
So, try to imagine trying to fix all the big bugs that you know about, then have to come here, read through ALL the posts and then log those requests down, prioritize them based on all the other work you have, make those changes, recompile, test, etc. It's not a easy and it gets frustrating. But believe me, when we do fix an issue or are able to give the users what they want, we get an extreme amount of satisfaction knowing that we were able to satisfy the "customer".
So please, be careful what you state about devs. Those that do read here usually have thick skins, but complain enough, and they might just quit and then you have nothing.
I understand where people are coming from, but you've been blaming the devs when it's not their fault. Again, the android source is huge and it takes more than one person to work on it. Especially if they are responsible for more than one device. Some devs are working on source for more than just this phone. So, add that to what I already stated and hopefully, you can begin to understand what the devs are going through.