Related
This is not intended to be mean to the ap team but i am posting this because i feel they should of been honest to us from the beginning and just said we can't release yet. My reasons for feeling this way are listed below
1. About 1 month after pk3 dual was released, pawel and the rest of the team changed their signature to rom: top secret and it had been like that even after hdubli posted a ported copy of wm6.1.... why did'nt pawel post a wm6.1 rom when he changed rom to top secret?
2. the team keeps saying stuff like we have a BT bug or screen problems and i realize that there are some updates on the ati driver and stuff but the BT stack that is on the wm6.1 that hdubli released works great. i can use a BT mouse and a BT keyboard, and BT headphone all at the same time and it works great. I can provide a vid if there are doubts
3. Most is importantly even BoyGeniusReport says http://www.boygeniusreport.com/2008/03/28/htcs-manilla-gets-screenshotted/ this rom is from the x7510. something i said on the "Athena Project 4.0 coming, but needs...." post 228 but pawel denied this is post 229
in conclusion everyone should stop looking for the release of this rom and start looking for the release of the x7510 cause then and only then will this rom be released. I am only posting this so people can have a realistic outlook on the rom and can stop being dissapointed everyday in the hope it will be released. I did not post this to come down on the team i just feel like there is so much tension on this fourm and i wanted to make my thoughts known.
High Five
Hypothetically speaking...
... Even if this were the case, why would you want him to release pre-release software that could get him in trouble or again, hypothetically, his *source* in trouble? People get fired for leaking stuff, sometimes worse. Personally, I don't need to know where this stuff comes from.
How about we let him work on things and hey, at least there's a better chance that he'll be able to bring us more HTC gems for a possible v5.0.
ok dude the rom is a 7510 rom but no way do i have to wait for it to be released. there still isn't a solid release date. the rom i could give u right now but it needs to properly be tested and bugs be fixed. we release with bugs, u guys complain, we look bad. i can take complaining before the rom then praises when it comes out.
also we have had 6.1 for a while. something like november i got the first athena 6.1 rom with build 19145 if im not mistaken. we have had 6.1 even before that though.
toastedlogic said:
... Even if this were the case, why would you want him to release pre-release software that could get him in trouble or again, hypothetically, his *source* in trouble? People get fired for leaking stuff, sometimes worse. Personally, I don't need to know where this stuff comes from.
How about we let him work on things and hey, at least there's a better chance that he'll be able to bring us more HTC gems for a possible v5.0.
Click to expand...
Click to collapse
1st i never said once that he should release it. what is said was he should tell us he cant release it. i don't remember anywhere in my post and any post for that matter where i said "you should release it right now even if it will get you into trouble or even if its not ready"
On a side note - i also live in orlando, fl and goto ucf do you play halo?
Go Knights!
irus said:
1st i never said once that he should release it. what is said was he should tell us he cant release it. i don't remember anywhere in my post and any post for that matter where i said "you should release it right now even if it will get you into trouble or even if its not ready"
On a side note - i also live in orlando, fl and goto ucf do you play halo?
Click to expand...
Click to collapse
No kidding - I'm planning on getting back to school this fall myself. Live right around the corner from the Uni. No Halo, since my box was red-lighting again just before my damn cat knocked a cup of water over onto the PSU for it. So i've got a little bit of work to get my box working again... oh yeah and I was banned from Live just before all that too (modded firmware), so yeah I did play halo. Meh
Pawel062 said:
also we have had 6.1 for a while. something like november i got the first athena 6.1 rom with build 19145 if im not mistaken. we have had 6.1 even before that though.
Click to expand...
Click to collapse
but that is my main point for saying that you can't release it yet. you had wm6.1 since november but released a cooked wm6 rom in late november. Don't get me wrong i am grateful for everything you have done and the only point i am trying to make is that you have to wait to release. I have logical points for these thoughts. example: in "Stop the stupid ap 4.0" post 36 - you told someone you have 2 newer builds than 9.5 build 405 but you can't release it.
Look im not trying to get into a pissing match with you, and nothing productive will come out of us arguing back and forth. So if you say it's still buggy and you need more time to test than its buggy and needs more time to test. i will not say another word about it.
High Five
PAWEL as I said before: this ISN'T a CUSTOMER'S forum, this is a DEVELOPER'S forum.
Customer want the best (and irrealistic) ROM, a developer want TO DEVELOP and share knowledge, so we are ready to a BUGGY one, you aren't a company. WE LIKE TO PLAY , we aren't customers, again!
Just as an example, I don't care about BT bug, I am pretty sure I have it fixed in a couple of days .A developer forum is a place were people exchange beta, and fix bug, together.
In the excalibur forum, without any "secret" rom, without any "project" , even without any DONATE, kavana (China) posted a rom, rick (GB) improve it, we worked togeter with kavana and rick, now we have TWO good rom!
Release a working, buggy version, believe me, may be you will surprised how people here will be fast to find AND FIX bugs.
Knowledge is something widely spread here and on the NET too! USE THE FORCE LUKE (the force is the NET and the spread knowledge). If you don't trust the FORCE you can't win!
sergiopi said:
PAWEL as I said before: this ISN'T a CUSTOMER'S forum, this is a DEVELOPER'S forum.
Customer want the best (and irrealistic) ROM, a developer want TO DEVELOP and share knowledge, so we are ready to a BUGGY one, you aren't a company. WE LIKE TO PLAY , we aren't customers, again!
Just as an example, I don't care about BT bug, I am pretty sure I have it fixed in a couple of days .A developer forum is a place were people exchange beta, and fix bug, together.
In the excalibur forum, without any "secret" rom, without any "project" , even without any DONATE, kavana (China) posted a rom, rick (GB) improve it, we worked togeter with kavana and rick, now we have TWO good rom!
Release a working, buggy version, believe me, may be you will surprised how people here will be fast to find AND FIX bugs.
Knowledge is something widely spread here and on the NET too! USE THE FORCE LUKE (the force is the NET and the spread knowledge). If you don't trust the FORCE you can't win!
Click to expand...
Click to collapse
i totally agree with you..... and also im pity of those who donated
tomary said:
i totally agree with you..... and also im pity of those who donated
Click to expand...
Click to collapse
oooouch, i think that might be a little harsh. You forget they have already posted 3 roms so i think the people who have donated got their moneys worth
My first thought for the team is if you WANT to release, then there's nothing wrong with realeasing a beta--paid software makers do it all the time. Here is a beta with known bugs. Da-ta-da-tada. There's likely unknown bugs too--user beware. That's why its beta. Heck, while its not as optimal,some companies (cough, cough, microsoft,) can release betas as the real deal.
For free (please donations accepted look at the value) roms/software, the bar shouldn't be higher than that of the commercial stuff.
It's funny how this just suddenly went down hill with all the slandering etc etc... I appreciate the time EVERYONE on the AP Team took to make what was (and most of us if not ALL enjoyed it) and what is to be. I personally donated as a sign of gratitude and saying thank you, heck I would've donated if they had even asked for some sort of donation just to teach how they did it instead of releasing a new ROM. Some of you guys are just down right ungreatful and quickly forget all the hard work and time they Team puts in to stand behind their wonderful ROMS. And lets not forget the tons of apps they cook in the ROMS too. So what's the big deal if people want to donate I did it and I'll be doing it again in the near future.
If the team DOES NOT want to release. That is the team's perogative also. This seeming to hang forever on the edge of release is a little nerve wracking and is hard on the fan base,but so what? If we, the fan base, donate less--really--donations are piddly anyway. The team needs to do what they do for the fun of it and the satisfaction of it.
I think it's about time this ROM was released, bugs'n all. Just release as a Beta.
irus said:
but that is my main point for saying that you can't release it yet. you had wm6.1 since november but released a cooked wm6 rom in late november. Don't get me wrong i am grateful for everything you have done and the only point i am trying to make is that you have to wait to release. I have logical points for these thoughts. example: in "Stop the stupid ap 4.0" post 36 - you told someone you have 2 newer builds than 9.5 build 405 but you can't release it.
Look im not trying to get into a pissing match with you, and nothing productive will come out of us arguing back and forth. So if you say it's still buggy and you need more time to test than its buggy and needs more time to test. i will not say another word about it.
High Five
Click to expand...
Click to collapse
thanx just dont like people saying i cant release this until the 7510 is out. i released snapvue before the shift was out and that was ok. i'll also release this new rom before the 7510 is out. i'll also be able to provide details when the 7510 is out and about what the price should be.
sergiopi said:
PAWEL as I said before: this ISN'T a CUSTOMER'S forum, this is a DEVELOPER'S forum.
Customer want the best (and irrealistic) ROM, a developer want TO DEVELOP and share knowledge, so we are ready to a BUGGY one, you aren't a company. WE LIKE TO PLAY , we aren't customers, again!
Just as an example, I don't care about BT bug, I am pretty sure I have it fixed in a couple of days .A developer forum is a place were people exchange beta, and fix bug, together.
In the excalibur forum, without any "secret" rom, without any "project" , even without any DONATE, kavana (China) posted a rom, rick (GB) improve it, we worked togeter with kavana and rick, now we have TWO good rom!
Release a working, buggy version, believe me, may be you will surprised how people here will be fast to find AND FIX bugs.
Knowledge is something widely spread here and on the NET too! USE THE FORCE LUKE (the force is the NET and the spread knowledge). If you don't trust the FORCE you can't win!
Click to expand...
Click to collapse
thats why if i cant get it to my liking by friday it will be released as a beta. the 19181 build was just to unstable. it got un usable after a while. u really wanted me to release that? we tried to make it better and got it to about 80% of what it should be but then decided to go for the new 19202 because we got the ok for that. by friday there will be a rom. if all goes well before that u might have a non beta build.
tomary said:
i totally agree with you..... and also im pity of those who donated
Click to expand...
Click to collapse
you are really getting out of hand. u donate if u like. i provided 4 roms to everyone already. people wanted a vanilla so im making a vanilla. i guess u can't make everyone happy.
Pawel062 said:
thats why if i cant get it to my liking by friday it will be released as a beta. the 19181 build was just to unstable. it got un usable after a while. u really wanted me to release that? we tried to make it better and got it to about 80% of what it should be but then decided to go for the new 19202 because we got the ok for that. by friday there will be a rom. if all goes well before that u might have a non beta build.
Click to expand...
Click to collapse
If you don't mind I don't like getting my hopes up (again). So I'll put it on my calendar for Friday. I'm not hoping for it to be released before that (or maybe I am but trying not to). Dare I say it...? You're not going to disappoint us are you?
And please note. I greatly appreciate your hard work. That’s why I donated! But checking every day to find out that it’s not released it getting a bit tedious . Considering it has been hanging close to being released for quite some time now.
Awaiting delivery
it will be 100% out on friday. whether in beta form or final form. it'll most likely be afternoon local time because thats when i'll have time to release. i would like a tuesday release though because would be very funny... dont u agree??
Pawel062 said:
it will be 100% out on friday. whether in beta form or final form. it'll most likely be afternoon local time because thats when i'll have time to release. i would like a tuesday release though because would be very funny... dont u agree??
Click to expand...
Click to collapse
A few questions (if you don't mind, if you do just don't answer ):
Will the beta be usable? (maybe good to know for less experienced people);
What's your timezone?
NB: no not funny at all, as I said: I'm not getting my hopes up again.
So, new to this game, but a reasonably good tech head by trade. I didn't see any information outlining the differences between the available GTab ROMs in an apples to apples sort of way. Does anything like that exist currently? If not, is this something the community would be interested in brainstorming in a Google Doc or something? I'm happy to get things rolling if so.
Okay, so, this might be stupid, or a total waste of time, but what the heck:
https(colon,slash,slash)spreadsheets.google.com/ccc?key=0Au8YYie-Ky7kdDNQRG8zN09xYnQ2NTVvOXY1ZTFtMXc&hl=en&authkey=CJC3j5oC
I went ahead and started working up a spreadsheet. Feel free to go in and start editing, adding important features, correcting, or whatever else. If someone else has beaten me to this, just say so.
I actually think it is an awesome idea and should help a lot of people decide what ROM they want to use. I have had my GTab since Christmas and have flashed mine over 20 times. I have tried all of the ROMs available on these forums multiple times and I don't think I would have needed to if a spreadsheet like this was in place earlier.
Okay, I think I seeded the spreadsheet with as much information as I can based on the various ROM threads. It'll be up to the community to help fill in some of the remaining gaps and such. And feel free to add in new feature checkpoints as well that users would find relevant. I'll keep curating the document to keep it consistent, and will fill in more once I actually have my G-Tablet in hand.
Features, add features that we could us, so those of us who want a rom that performs the tasks we want can see which one best suits us.
just some egs
bluetooth gps support
usb gps support (dont think this will be possible till hc is availabe)
usb g3 support
proxy support
external or bt keyboard and mouse support
.....
TheQuicksilver said:
Okay, so, this might be stupid, or a total waste of time, but what the heck:
https(colon,slash,slash)spreadsheets.google.com/ccc?key=0Au8YYie-Ky7kdDNQRG8zN09xYnQ2NTVvOXY1ZTFtMXc&hl=en&authkey=CJC3j5oC
I went ahead and started working up a spreadsheet. Feel free to go in and start editing, adding important features, correcting, or whatever else. If someone else has beaten me to this, just say so.
Click to expand...
Click to collapse
Neither stupid nor a waste of time: I have been wanting to do something similar for a while - decide what/whether to upgrade my TNTLite 2.2 install to, I just haven't found the time or energy.
Your spreadsheet is very helpful. You should start a thread for it in the 'G Tablet Android Development' forum and see if you can get it stickied: I'll bet a LOT of other people will find it useful too. Maybe the various developers will chime in and help you fill in the blanks.
*thumbs up!*
I for one thank you for your time and effort. I am waiting on my Gtab to be delivered and am trying to decide which ROM to use. With this spreadsheet I can see the pros/cons of the major players at a glance. I think I will go with Vega.
Tt
Icedvoco said:
Features, add features that we could us, so those of us who want a rom that performs the tasks we want can see which one best suits us.
just some egs
bluetooth gps support
usb gps support (dont think this will be possible till hc is availabe)
usb g3 support
proxy support
external or bt keyboard and mouse support
.....
Click to expand...
Click to collapse
Tossed some extra fields in for those requests.
999pings, thanks, I'll start a second thread once I have the requisite posts to do so in the Developer forum. I was sort of torn what the right place was to post this to begin with. Mods, feel free to merge the threads if necessary once I get the second one going.
Yeah thanks this would be helpful. It's always easier to have a side-by-side comparison than having to read through a long list of change logs and hundreds of pages of comments on what works and what doesn't. I too am waiting for my tablet to come in the mail and deciding which ROM to go with. I was basing my decision on popularity and that award going to TnT based on thread activity. Of course that doesn't always mean it's the best choice. I'd like to see this spreadsheet take shape in the next few days or so
Perhaps you can model yours after one that SimonNWalker here at XDA did:
http://db.androidspin.com/androidspin_release_matrix.asp
Something along those lines would be nice once I have the data put together from everyone. Likewise, it'd be nice to find a wiki for it to live on, some place that it could continue to be maintained over time. Ideally something like this can take off in a way that it wouldn't need me (or any single person) to constantly curate it.
TheQuicksilver said:
Likewise, it'd be nice to find a wiki for it to live on, some place that it could continue to be maintained over time. Ideally something like this can take off in a way that it wouldn't need me (or any single person) to constantly curate it.
Click to expand...
Click to collapse
I don't know much about it, but there is Wiki functionality within XDA if this gains popularity. The spreadsheet/chart can definitely grow over time especially when Honeycomb comes out. There will be many more flavors of ROMs being released.
http://forum.xda-developers.com/wiki/index.php?title=Main_Page
Dave615 said:
I don't know much about it, but there is Wiki functionality within XDA if this gains popularity. The spreadsheet/chart can definitely grow over time especially when Honeycomb comes out. There will be many more flavors of ROMs being released.
http://forum.xda-developers.com/wiki/index.php?title=Main_Page
Click to expand...
Click to collapse
Oh, fantastic. That'll do great. I'll check into porting the stuff over to that once things fill in. Loves me some wiki action.
g1no23 said:
I actually think it is an awesome idea and should help a lot of people decide what ROM they want to use. I have had my GTab since Christmas and have flashed mine over 20 times. I have tried all of the ROMs available on these forums multiple times and I don't think I would have needed to if a spreadsheet like this was in place earlier.
Click to expand...
Click to collapse
I agree, excellent idea. Thanks for taking the time to do this!
I was about to embark upon getting VPN access working using TNTLite, now I know that I can switch to Vegan if it gets too complicated.
Here is the link since I thing the OP could not post it up
https://spreadsheets.google.com/ccc...NTVvOXY1ZTFtMXc&hl=en&authkey= CJC3j5oC#gid=0
copc said:
Here is the link since I thing the OP could not post it up
https://spreadsheets.google.com/ccc...NTVvOXY1ZTFtMXc&hl=en&authkey= CJC3j5oC#gid=0
Click to expand...
Click to collapse
Yeah, thanks. Forums require a minimum of 8 posts to include links. I just joined, so had to fake it a little, heh.
Thankyou TheQuicksilver!!
Sticky??
I suggest adding a column for stock TNT, and maybe even 1 for stock+enhancement?
That would be helpful for those trying to decide to stay stock or not.
Jim
TheQuicksilver said:
Okay, so, this might be stupid, or a total waste of time, but what the heck:
https(colon,slash,slash)spreadsheets.google.com/ccc?key=0Au8YYie-Ky7kdDNQRG8zN09xYnQ2NTVvOXY1ZTFtMXc&hl=en&authkey=CJC3j5oC
I went ahead and started working up a spreadsheet. Feel free to go in and start editing, adding important features, correcting, or whatever else. If someone else has beaten me to this, just say so.
Click to expand...
Click to collapse
Brand new to the GTab.. Picking a ROM and rooting tonight. This resource helps immensely! Thanks!
Just wanted to say thanks for this. This would be great to have as a "sticky" so we don't have to search for it, and for new owners to see at the top of the page.
Why was I getting that error? It's gone now I just want to make sure it's answered for everyone else. I was flashing a rom and it was doing that. Do a reboot. Your system wont be there so reboot into botoloader and go back into recovery.
I'm getting the same error when trying to flash and when I reboot I can't get past the htc screen. I'm using the twrp recovery and I have tried resetting a few times.
EDIT**
I tried resetting my phone a couple more times and it finally just worked. I have no clue what causes this.
Original poster is correct, this method works for whatever reason. I tried it twice now.........
Same thing
Trying to flash a kernal. I tried several reboots of bootloader and recovery and no luck. I am going to flash clockwork since I am using team wins recovery and see if that works.
Same exact thing......OP's solution worked......Thank you
Yeah had this error too. I think it happens when you try to flash a different kernel on the stock ROM. After I switched to a different ROM the error went away.
Sent from my PG86100 using Tapatalk
I'm having the same issues, but rebooting isn't helping. TWRP needs to be updated to address this issue. Until then, no ROMs for me.
That error will usually occur with signature verification failures, you need to make sure that signature verification isn't turned on when installing an unsigned rom.
It would make sense if this has to do with permissions, but I have signature verification turned off in the bootloader. Is there somewhere else that signature verification needs to be turned off?
I'm getting this error trying to root the phone using the sticky guide. It happens when I try to flash the superuser file.
what the op said worked for me as well...restarted and everything worked fine
Don't waste your breath guys.
I've tried diligently to work with the devs of TWRP trying to resolve a number of outstanding issues and polish it up and they don't seem to be receptive.
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/12
myn said:
Don't waste your breath guys.
I've tried diligently to work with the devs of TWRP trying to resolve a number of outstanding issues and polish it up and they don't seem to be receptive.
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/12
Click to expand...
Click to collapse
Diligently work with the devs? Like this "issue" ?
http://github.com/TeamWin/Team-Win-Recovery-Project/issues/6
and this:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/7
?
And for everyone in this thread, this issue has been covered many times in our thread. It's due to compatibilities with the updater-binary and accompanying script. As we have adopted update-binary api 3, and sideload errors are because the rom/zip is trying to issue an api command no longer supported in api3. Get your nice "devs" to update their scripts.
I was receiving this error for two days after s-off and updated recovery. I was breaking my head trying to figure out a solution. I tried everything from switching recoveries to even pushing SU again. I also downloaded ROMe using my pc and my phone bc many ppl were calling the ROMs "corrupted." Nothing worked. I even received hate mail from multiple XDA members bc I was posting "too" many questions "without" searching the forum.
Solution, changing out my SDcard. LMAO, yes I know, wanted to run through a wall bc i had thought of it right off the back but did not want to believe my 32 gig card was causing the problem. I replaced with the card that came with the phone and BAM have been switching ROMs ever since.
Food for thought.
AssassinsLament said:
Diligently work with the devs? Like this "issue" ?
http://github.com/TeamWin/Team-Win-Recovery-Project/issues/6
and this:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/7
?
And for everyone in this thread, this issue has been covered many times in our thread. It's due to compatibilities with the updater-binary and accompanying script. As we have adopted update-binary api 3, and sideload errors are because the rom/zip is trying to issue an api command no longer supported in api3. Get your nice "devs" to update their scripts.
Click to expand...
Click to collapse
Recovery can be a pretty scary place for many folks, For you and I this is our bread and butter, for most it's a rare visit. My goal in everything I've ever developed is to make things easier, friendly and inviting.
One of the many patterns you can use to accomplish this is to use professional and consistent verbiage and provide verbosity where it is appropriate. Usability 101.
I am sorry but "Backup Naowz!" is not clear and certainly not professional. This pro-treys no confidence that the following action is actually going to work.
Regarding the Original Posters message about this error which I also experienced. If this is common and you can trap it through exception handling, why not present a user friendly message to the user?
As I mentioned on IRC, I want this to be a polished product. I really think this can develop into one great recovery but right now it needs a little help. When you're ready to listen, I'm willing to help.
myn said:
Recovery can be a pretty scary place for many folks, For you and I this is our bread and butter, for most it's a rare visit. My goal in everything I've ever developed is to make things easier, friendly and inviting.
One of the many patterns you can use to accomplish this is to use professional and consistent verbiage and provide verbosity where it is appropriate. Usability 101.
I am sorry but "Backup Naowz!" is not clear and certainly not professional.
Regarding the Original Posters message about this error which I also experienced. If this is common and you can trap it through exception handling, why not present a user friendly message to the user?
As I mentioned on IRC, I want this to be a polished product. I really think this can develop into one great recovery but right now it needs a little help. When you're ready to listen, I'm willing to help.
Click to expand...
Click to collapse
First off, who really cares about "Backup Naowz!" being an issue but you? I mean seriously, you're just trolling. So do you go tell people they can't speak improper english because you don't like it? Come on. We do this for free, for fun. If you paid us to make this recovery for you, then sure, if what you want is Backup Now!, we can do that for you. But you are using it for free. At least feel grateful of what we've done as a hobby for everyone instead of nitpicking 10+ issues on the smallest inaccuracies that go against your perfect world. Seriously, I'm sure others might like the "Backup Naowz!". Anyways, if you have any suggestion or comments, feel free to do it in our thread, instead of drawing up 10+ issues that are more like "hey can you add this for me? do this for me? change this for me?" issues.
And now you go and try to make it seem like we don't care about helping our users? Nice try.
Here's the zip that was giving me the sideload errors.
I don't see any issues with the updater-script and the updater-binary is ver 3.
myn said:
Recovery can be a pretty scary place for many folks, For you and I this is our bread and butter, for most it's a rare visit. My goal in everything I've ever developed is to make things easier, friendly and inviting.
One of the many patterns you can use to accomplish this is to use professional and consistent verbiage and provide verbosity where it is appropriate. Usability 101.
I am sorry but "Backup Naowz!" is not clear and certainly not professional. This pro-treys no confidence that the following action is actually going to work.
Regarding the Original Posters message about this error which I also experienced. If this is common and you can trap it through exception handling, why not present a user friendly message to the user?
As I mentioned on IRC, I want this to be a polished product. I really think this can develop into one great recovery but right now it needs a little help. When you're ready to listen, I'm willing to help.
Click to expand...
Click to collapse
i completely agree with polish and consistency portraying professionalism, and we're glad for and always open to suggestions. however, in this case, we purposely used that terminology. we, as teamwin, like to have fun with our projects. some of them are very serious (wimax, hdmwin, kernel manager). others are a bit more on the entertaining side (theninjatweeter, twinpic 3d). with the recovery, we wanted to do something that stood apart from the rest. we do things that reflect our personality as a team.
as for the sideload issues that many are experiencing, we've discussed many times in our threads as well as on twitter and even google+; it is an issue with an outdated updater-binary script. update the scripts, no more sideload errors.
to come out and say we're not willing to listen to suggestions seems a bit presumptuous, even dangerous, when the issues you put on our github were more along the lines of requests.
AssassinsLament said:
...
if you have any suggestion or comments, feel free to do it in our thread, instead of drawing up 10+ issues that are more like "hey can you add this for me? do this for me? change this for me?" issues.
And now you go and try to make it seem like we don't care about helping our users? Nice try.
Click to expand...
Click to collapse
I apparently didn't realize that your thread was the official authoritative record for bug tracking. As your code is on github I thought the issue/request tracking would be a far better medium to track these. Hence why github has this feature Interestingly enough 4 of the 10 features/bugs you implemented in your 1.3 TWRP release were reported by me at your github issue repo so apparently this is quite effective
Don't worry about the number of issues/requests out there or who put them in. I've got over 250+ issues/requests reported on Synergy and the thing went gold yesterday. Filter your issues/requests by priority and address them top down from highest first. Some you'll never get to and that's fine .
Again, all I want to provide is a better experience for my users who I can hopefully promote to use TWRP. Please don't shoot the messenger.
myn said:
I apparently didn't realize that your thread was the official authoritative record for bug tracking. As your code is on github I thought the issue/request tracking would be a far better medium to track these. Hence why github has this feature Interestingly enough 4 of the 10 features/bugs you implemented in your 1.3 TWRP release were reported by me at your github issue repo so apparently this is quite effective
Don't worry about the number of issues/requests out there or who put them in. I've got over 250+ issues/requests reported on Synergy and the thing went gold yesterday. Filter your issues/requests by priority and address them top down from highest first. Some you'll never get to and that's fine .
Again, all I want to provide is a better experience for my users who I can hopefully promote to use TWRP. Please don't shoot the messenger.
Click to expand...
Click to collapse
Again, I don't mind real issues... That's not my point. My point is a lot of your so called bugs or issues are the way we cosmetically chose to do it. Your issues are more so opinions, and wish lists. There is a place for opinions, and a place for real bugs. That's all I am saying.
It would be on the same level as me using your bug/issue space to say "hey i don't like that color.", "hey, can you take off myn from everywhere in your rom, I like it without?" <--- these are NOT issues. These are just what I would like/want. Do you understand?
Anyhow, I am looking into your script. Sadly we do not have any documentation of the differences between api's but, I will try to figure it out. It looks simple enough, so it should work. I'll let you know.
After following the various video/text guides to install cm7 alpha 2.1 on the TouchPad, I am getting a weird error and non-responsive device.
I have installed cm7 on other TouchPads and had no problem. On this one it re-boots to a screen which says, "Please release keys...". There is no combination of keys which fixes this. Only thing which has worked is to Doctor it.
The only thing different on this TP is that it is the ATT 4G version, which uses a different ROM/Doctor.
I've been searching various forums for 3 days and haven't seen anyone else with this problem.
amenditman said:
...The only thing different on this TP is that it is the ATT 4G version, which uses a different ROM/Doctor.
I've been searching various forums for 3 days and haven't seen anyone else with this problem.
Click to expand...
Click to collapse
Really?? I'm shocked! The search function must be broken, I've read at least 20 or 30 threads on this problem...
Considering they're as common as dirt, the Cyanogen touchpad team certainly must had access to that particular model and I have no doubt ensuring the compatibility & functionality of the alpha on that particular model of hardware was their absolute top priority!
I honestly can't imagine what must have precipitated this unforeseen calamity! Fear not! I'm sure the greatest minds on this forum are feverishly working, day & night, without food or bathroom breaks, to determine the root of this dysfunction using the spare ATT 4G Touchpads they had sitting around, relegated to propping doors open, leveling wobbly tables, etc...
over in the rootz forum for CM, apparently, this is a known issue for the 4G models, copmatibility is not yet available, but it is reported on the bug list so im sure it will be fixed, but as usual, no eta's!
Solidus_n313 said:
over in the rootz forum for CM, apparently, this is a known issue for the 4G models, copmatibility is not yet available, but it is reported on the bug list so im sure it will be fixed, but as usual, no eta's!
Click to expand...
Click to collapse
Thanks, I didn't see that in my internet searches.
Could you point me to the bug in the list? I can't seem to find it or at least I don't want to open a duplicate one.
its issue #398
http://code.google.com/p/cmtouchpad/issues/list?num=100&start=100
link might get removed, but its the open issues list, 2nd page (was apparently reported today, was it you? ;P)
also, i know dalingrin adresses the issue in the thread, but may be something on the back burner for future release and not requested on bug list per se
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.