Crazy as idea...use our old devices for shared computation - Verizon Samsung Galaxy S 4

Guys and Gals, we have been struggling with unlocking the S4 Bootloader for well over a year. I stay current with where our progress is. I'm not a developer and i know this is a crazy suggestion but what have we got to lose?
Why don't we pool our old devices and use OpenCL (or similar) to tap into our phone GPUs and try a targeted attack on our bootloader? Yes, I know, I know it will take a billion years for a million supercomputers to brute force the SHA1 key. But headway has been made in the last year in finding ways to target attacks on SHA1. I'm not saying it will be easy...it won't. Hell, I don't even know how to get started but that's why I bring the request to you guys. I have 2 or 3 old devices....we all do. Plus if we continue this then every year each of us is adding a device to the computational network.
I know there will be many "nay-sayers" so don't post with negativity. If you are interested and want to contribute then post and let me know.
@Surge1223 @joshuabg @ryanbg @NighthawkXL @RuggedHunter @SamuriHL

I like the idea but this could take a very long time, but there is a chance that one of the first keys we gen is the right key. And why exactly did you mention me?
Sent from my OtterX running AICP using Tapatalk

Why utilize under powered devices?
http://www.infosecurity-magazine.com/news/sha-1-crypto-protocol-cracked-using-amazon-cloud/
I'm going to bow out, though, as I'd only be one of the naysayers on this.

joshuabg said:
I like the idea but this could take a very long time, but there is a chance that one of the first keys we gen is the right key. And why exactly did you mention me?
Sent from my OtterX running AICP using Tapatalk
Click to expand...
Click to collapse
Because you keep up with the threads on our bootloader, so I figured you would have some interest.

SamuriHL said:
Why utilize under powered devices?
http://www.infosecurity-magazine.com/news/sha-1-crypto-protocol-cracked-using-amazon-cloud/
I'm going to bow out, though, as I'd only be one of the naysayers on this.
Click to expand...
Click to collapse
Because they are free. Our community doesnt have a good track record for paying for research and development to benefit themselves directly, much less benefit the greater good. I didn't post to claim I have THE answer...I posted with a crazy ass idea which I hoped would spark some ingenuity in others. Anyway, thanks for the link and thanks for being honest.

Hash Collisions
Finding a hash collision isn't like bruteforcing a password. It's (very basically) finding another file that has the same hash. It's not so much guessing the 'password' as it is hoping that mathematical computation outputs the same hash as another file, by sheer chance. There are academic and private researchers who have been working on this for years, with exponentially more processing power and resources than we could ever hope to see. While I admire your will to find a solution, this won't be happening for us. Your efforts are more fruitful by calling Samsung/Verizon/AT&T and complaining, leaving feedback, and doing it relentlessly. I call/email/chat with Samsung and Verizon on a daily basis, leaving feedback and asking to have my bootloader unlocked. If enough fuss is made, they may come around. Verizon and AT&T are the main targets, I just call Samsung when Verizon gets sick of hearing me.
To put it into perspective, you have a greater chance of winning the powerball 100 times, and getting hit by lightning every time you go to collect your prize.

Even today's most basic quantum computers that are being developed could theoretically take years to crack SHA1 (when used properly), granted it could do it in much less time then any Von Neumann machine could do. But nonetheless it's unrealistic to use this as a method to crack encryption. You'd have a better chance getting the NSA to provide the info on backdoors they have (assuming the Snowden leaks are true) that they have broken nearly all modern encryption by providing researchers with a flawed RNG.

Related

Bootloader Unlocking Effort

Hey all,
I've been a lurker for a while, been looking for a way to encourage the now Google-owned Motorola Mobility to unlock their bootloaders much like HTC has wisely done, but it's becoming more and more obvious to me that they don't care about the "minority" of us that actually feels as though we are entitled to full admin rights on our phones that we either paid a ton of cash for, or signed a lengthy contract to obtain. Verizon is the one blocking it? HTC found a way, and so can Motorola Mobility...that is cop-out.
My proposal is that there be an effort to unlocked the bootloader, I am not some expert programmer, and I am open to whatever will help the cause. I know there was a bounty on it, but to me this isn't about money, I'll donate time, money, information ripped from my phone if it, in some way, contributes to unlocked that bootloader. Even if you need my unused CPU cycles to calculate things, I don't care, just tell me what I can to do help, because I am sick of not being able to use my phone to it's fully potential.
Maybe I am being naive, but I believe if we all worked together we could accomplish this goal. If you agree, please, let's organize and figure this out!
-Joshua
I love optimism
I'm down with the movement...
This phone does have mad potential to be so limited compared to other phones.
I just can't believe that we are running an unofficial, incomplete version of CM7 and it runs smoother than stock Blur.
Is that telling you something about Motorola?
Do you guys think Google will make that decision for Motorola or will Moto stay the same?
Sent from my Android
Worth a try...
Re: Google changing Moto policy
I don't know so much about Google changing Motorola's stance on the locked bootloader, we've tried petitioning the company themselves, but have we tried petitioning Google? Or maybe it's too soon, maybe they are working on it right now? Hard to tell, and I don't want to put pressure on Google too soon especially if they are trying diligently right now to do the right thing.
But the above poster is right, cracking it ourselves is definitely worth a try. I have contacts (unfortunately know inside Motorola), I know people with lots of knowledge on encryption, I'll be honest one of my friends does have a knack for the impossible, but this would be too much for one lone person. I also have a few computers in the house, to donate computing power. None above 5 GB of RAM unfortunately, but my friend with all of that know-how does also have a synchronous 20/mbit up/down connection to the net, if that helps, and I have another friend that is the linux admin at a an unnamed private university in Durham that might could lend a hand in some way.
We have the resources, we just need to pool them.
Someone with the realistic technical know-how, just tell us where to begin, and the shortest path to getting to our goal and we'll do all we can to contribute!
Thanks for understanding and not just writing this off as a pipe-dream...because I know if we work together we can accomplish almost anything.
-Joshua
spyda256 said:
I don't know so much about Google changing Motorola's stance on the locked bootloader, we've tried petitioning the company themselves, but have we tried petitioning Google? Or maybe it's too soon, maybe they are working on it right now? Hard to tell, and I don't want to put pressure on Google too soon especially if they are trying diligently right now to do the right thing.
But the above poster is right, cracking it ourselves is definitely worth a try. I have contacts (unfortunately know inside Motorola), I know people with lots of knowledge on encryption, I'll be honest one of my friends does have a knack for the impossible, but this would be too much for one lone person. I also have a few computers in the house, to donate computing power. None above 5 GB of RAM unfortunately, but my friend with all of that know-how does also have a synchronous 20/mbit up/down connection to the net, if that helps, and I have another friend that is the linux admin at a an unnamed private university in Durham that might could lend a hand in some way.
We have the resources, we just need to pool them.
Someone with the realistic technical know-how, just tell us where to begin, and the shortest path to getting to our goal and we'll do all we can to contribute!
Thanks for understanding and not just writing this off as a pipe-dream...because I know if we work together we can accomplish almost anything.
-Joshua
Click to expand...
Click to collapse
i love your optimism i have some old pms that may help with the effort
SHA-1 brute force can be cracked for around $2 of Amazon cloud computing service.
http://www.geek.com/articles/news/r...for-2-10-with-amazons-cloud-service-20101122/
Isn't boot loader use SHA-1 encryption?
(of course, the key may be much longer, but it may not be impossible for cheap. I say try to pool together like $100 and try Amazon cloud computing a try?)
Re: Amazon
hpark21:
I like the way you're thinking, does anyone else think this might be a good call? I know there was a bounty of around ~$800 somewhere, so I doubt if all of us who rightfully were promised and unlocked bootloader wouldn't mind pooling a bit of money for the computing power, hell I myself would give $50 to the effort if we knew it was a viable solution.
Other thoughts?
Also, ztotherad, if you could send me those PMs maybe we can sift through those and see if there are some other avenues, nothing is off the table at this point.
thanks again for coming together on this, that is the true meaning of community.
spyda256 said:
hpark21:
I like the way you're thinking, does anyone else think this might be a good call? I know there was a bounty of around ~$800 somewhere, so I doubt if all of us who rightfully were promised and unlocked bootloader wouldn't mind pooling a bit of money for the computing power, hell I myself would give $50 to the effort if we knew it was a viable solution.
Other thoughts?
Also, ztotherad, if you could send me those PMs maybe we can sift through those and see if there are some other avenues, nothing is off the table at this point.
thanks again for coming together on this, that is the true meaning of community.
Click to expand...
Click to collapse
i can def send you them, idk how much help theyll be
Uh, I think it's already been established that brute forcing it is impossible.
Stuckinabox said:
Uh, I think it's already been established that brute forcing it is impossible.
Click to expand...
Click to collapse
In one of the many threads concerning bootloader unlocks, I believe the chances of us finding it were determined to be 1mill:1. It would take us over a decade to manually come up with the key. I don't want to kill confidence, but I'd like to keep things relatively rational.
Sent from my MB870 using xda premium
Stuckinabox said:
Uh, I think it's already been established that brute forcing it is impossible.
Click to expand...
Click to collapse
it's been established that brute forcing is nearly impossible, not completely impossible
it is something that would take an insane amount of resources to accomplish , and/or time ,
it would really come down to "how lucky are we?" really, as in::: how lucky are we that we stumble across or know a genius that can crack it, stumble across needed files, etc...
good luck to all who try, I wish I could do anything to get us there, but I don't know the first thing when it comes to this stuff, don't give up the dream!
Basically, what it comes down to is:
Find out what their hash key is. (encrypted password)
Then, try to go through all valid characters and see whether the input matches the output hash.
If one is lucky and they used short enough password, then it will be quick to find.
If unlucky and they used really long password, then the answer is that we won't be able to find it in REASONABLE time. (I would say 1-2 months to be reasonable - at $2/hr, it would cost $48/ day).
Only issue is when do we stop?
hpark21 said:
Basically, what it comes down to is:
Find out what their hash key is. (encrypted password)
Then, try to go through all valid characters and see whether the input matches the output hash.
If one is lucky and they used short enough password, then it will be quick to find.
If unlucky and they used really long password, then the answer is that we won't be able to find it in REASONABLE time. (I would say 1-2 months to be reasonable - at $2/hr, it would cost $48/ day).
Only issue is when do we stop?
Click to expand...
Click to collapse
There was some kind of crazy algorithm applied to each character to generate the correct item for each number of the key, correct? We would have to come up with that too?
Sent from my MB870 using xda premium
THANK YOU! Finally ... a revived movement. I pledged $100 on another thread and I'm good for putting it toward an unlocked bootloader again!
To learn from one of the most influential groups of our generation ... anonymous utilizes botnets to pool computing resources ... if we get a tool that could function similarly, could we not pool 1000s of computers together to crack it faster? It would make what is not feasible for a small set of computers to do... feasible. If all most users have to do is download a tool that gives us access to processing power and bandwidth ... users will download the hell out of it.
Count me in.
[ sent from _base2 ]
Hope
I understand doubters, and odds are likely against us, but that's ok, no one person can do it, and maybe not just one method, but somehow we WILL get to our goal. Whether Motorola capitulates or we find a method to crack it, we will not have this awesome hardware go to waste.
I am not generally a "black hat" kind of person, but in this case we are in the right so far as I am concerned (please don't quote DMCA BS to me, lol) because they made a promise to their customers, and it will be kept, whether they like it or not.
So, I am with the above poster that mention he didn't know quite where to start, or where we have already made progress, but if someone can help us out, explain the process, we figure out how to move forward. (Please forgive the run-on sentence).
I've minimal experience programming, only VB.net, C++, and a bit of Java from college, and I do tier 2 desktop support for a bank these days, but on my off time I'd love to spend it on something worthwhile, all of you deserve this, and we'll make it happen.
Maybe it's the troubleshooter in me that sees the problem and says "oh no, there's a way, we just need to find it". I have a colleague, the one I spoke of before, he has a knack for doing incredible things, so once we have a breakdown of what we need to do, perhaps he can be of help.
So my friends, where do we go from here?
spyda256 said:
I understand doubters, and odds are likely against us, but that's ok, no one person can do it, and maybe not just one method, but somehow we WILL get to our goal. Whether Motorola capitulates or we find a method to crack it, we will not have this awesome hardware go to waste.
I am not generally a "black hat" kind of person, but in this case we are in the right so far as I am concerned (please don't quote DMCA BS to me, lol) because they made a promise to their customers, and it will be kept, whether they like it or not.
So, I am with the above poster that mention he didn't know quite where to start, or where we have already made progress, but if someone can help us out, explain the process, we figure out how to move forward. (Please forgive the run-on sentence).
I've minimal experience programming, only VB.net, C++, and a bit of Java from college, and I do tier 2 desktop support for a bank these days, but on my off time I'd love to spend it on something worthwhile, all of you deserve this, and we'll make it happen.
Maybe it's the troubleshooter in me that sees the problem and says "oh no, there's a way, we just need to find it". I have a colleague, the one I spoke of before, he has a knack for doing incredible things, so once we have a breakdown of what we need to do, perhaps he can be of help.
So my friends, where do we go from here?
Click to expand...
Click to collapse
sir, did you get my pms?
Re: PMs
Nope, just saw them, thanks for that!

A Little Explanation and Clarification for CM9

It has come to my attention that a few people have been misunderstanding a few recent posts by myself. This is post is to clear the waters up a bit and to explain my position as a developer here on XDA.
As many of you guys know, we're probably the most lively "dead" device on XDA. At least in my opinion that is. We have been through a lot as a community but we still manage to survive. But recently things have been getting a little tense.
I received this device last summer like most of you have. When I got it, I immediately started figuring out how to get CM7 on it. Problem is that it was my first Android phone and with all the ways that Motorola locked it down I had a lot to learn and no time to learn it. After I learned off and on how to get things working on the X2 during the NO free time I had last fall I cranked out a pretty much solid CM7 in a week.
Now for the explanation for CM9/ICS. Most people probably think that since I could crank out CM7 so fast that I would be able to do the same with CM9 and make it just as good and amazing as CM7. Although I had it booted on the first build, it was FULL of errors and the touch screen didn't even work. ICS and CM9 is definitely not as easy as CM7. CM7 was already a year and a half in the making and had most of the problems worked out on all the devices that when it finally came time for us, it would just as smooth as butter as soon as it was booted. CM9 hasn't had time to develop into a "smooth" ROM for most devices; especially non-official like ours. The code for the touchscreen to work wasn't even in CM9 on my first build, for example. The problems for CM9/ICS can be narrowed down to a few things:
Graphics Memory
No Official ICS
Kernel Improvements
Graphics Memory and No Official ICS: Due to the way that ICS handles the way it puts stuff on our screen we run into Video RAM (VRAM) problems on our device. Basically the routines that control it are expecting the memory to be mapped (stored) in a certain way in VRAM. On a device that has ICS officially, this isn't as big as a problem as the proprietary files (props) are coded to respond to those requests and mappings and as such run smoother. If a device doesn't have ICS, most it usually has a similar device in which props can be pulled and ran accordingly.
This is not the case for Tegra 2 phones as no Tegra 2 device has official ICS. In fact the Tegra kernel (just looked this up) is only at 2.6.34-rc3 officially and have a 3.1.10 kernel in developement (Motorola can update it again to .35 if they wish to do so like for the ATRIX). Because of the lack of an official Tegra 2 kernel for Linux 3.X, and likewise the props for such kernel, we can't have props that handle the requests the system is asking for. And even if another phone gets updated, we're locked and stuck, so It doesn't matter either way. This means that VRAM problems will probably always be there and that there is nothing that I can do for it. Best thing I can hope for (and this is slowly making it's way through CM9) is that the code in CM9 is updated to allow us to handle the VRAM differently like in CM7/GB.
Kernel Improvements: The kernel (that's supposed to be) for ICS is 3.0 or higher. This includes changes in memory as stated above, touchscreen handling, device interaction with the kernel and many others. That being said, we don't have those improvements thus causing problems. These include memory as stated above, touchscreen not working (obviously fixed), data usage not working, data monitoring not working, and a few various ways other routines to draw to the screen and handle other things (such as why Chrome is picky). Some of these can be backported (downgraded) to our kernel with mixed results.
Problem is they have to be complied with our kernel and must match the kernel version in every way. That is why the kernel check is in CM7 and CM9. I can slowly work through implementing these routines through drivers known as kernel modules (mods). I have made mods for data usage (with a few issues) and another one (which not sure what it's supposed to do yet). I cannot (as in it's impossible) write them to change the memory handling. If I could even build them the kernel won't let me load them due to routines of same name fighting for control.
Think of it like the phone is a car and you and your friend are in the front (the kernel routines) and you have the exact same name. Meanwhile, you have another friend in the back (the OS). The OS says, "Hey Routines Named the Same, grab the wheel and turn turn left!" You would turn it to your left, but your friend (the other routine) has a different view of what left is and instead wants to go to your right. Obviously some problems arise.
Regarding the Soft Keys Issue: I know a few of you guys are a little upset regrading the fact that I won't add the soft keys in there by default. I have a justifiable reason behind not adding them: our phone already has buttons.
Our phone was designed to have hardware buttons that separate from the screen. Adding more buttons to the screen for buttons that already exist is not advantageous. It also unnecessarily takes up screen space that makes our phone our phone. Now you may be thinking, "Well the GNex has the soft keys on the screen..." You are correct. But the screen itself has actually been extended (as in a non-standard physical height) to accommodate for the soft keys and also has no hardware buttons for the menu and home, etc. In fact! The Nexus S (a still HIGHLY developed for, supported device and previous "Google Phone") doesn't even have the soft keys enabled from the software directly available from Google themselves.
With that being said, XDA user csking33 has made the option of softkeys available to the public should you choose to enable it. He has it working on the current Alpha 4 and I look forward to him getting them working on Alpha 5 when I release it. You can download it here: http://forum.xda-developers.com/showthread.php?t=1727680.
That is just a short (believe me when I say it's short) explanation as to why ICS is just a FUN FUN FUN thing to work with.
Personal Problems (I have a lot): This is not meant to be a whine-a-thon, more of an explanation of why I can't be as dedicated as I'd like to be. I have explained why ICS is a pain, I'm here to give you a brief rundown as to why I (personally) can't just make things work. I am a student studying Aerospace Engineering (not Computer Science or whatever else). It has kept me so insanely busy that I can't even begin to describe how much little time I have. I spend all day at school and all night doing the homework for it. I was lucky (once) when my Flight Structures II homework only took 5 hours to do. With so many long homework assignments and group projects it's a miracle I even survive. Next semester will be worse because now I have to actually design and build a model plane from scratch that does whatever my professors says it has to do. This is includes the whole design, approval process, building, testing, breaking, fixing, getting approved again, get it flown, doing it's mission and presenting our project. All that on top of the homework I have to do.
Whenever I do get free time during the day, I try to spend it with my girlfriend and/or friends or (if it's a few days) I go to visit my family (this weekend I am, for example). Family and friends have always a top priority of mine since forever and I won't let a phone be the reason why I don't see them IF I see them. In fact the donation money you guys have supported me with is going to get new tires for my car before I go visit my family. It has also bought me spare batteries and cables for when I really mess things up.
After all this is said and done, I stay up to 4 am working on the phone so that you guys can have a semi-legitimate Android experience. I do it because I want to and because we as a community deserve it.
It saddens me to know that I'm (essentially) the only one left working on the X2. Others pop their head in every once and awhile to help or to do what they want and that is GREAT. I love it. I'm always more than willing to help others out if they ask. And all they have to do is ask. PM me here on XDA, join me in the IRC or tweet me on Twitter. I'll be sure to get to it eventually.
TL;DR:
CM9/ICS will be unstable for as long as I can see in the future. There is not much I can do.
No I won't enable soft keys, there is no point in a default build. See the post if you wish to enable them.
I'm a really, really busy man but I do what I can. You guys have helped tremendously in supporting my work and helping me live a little easier
Thanks for the explanation. At this point I guess all we can do is hope that someone at Motorola feels sorry for us and leaks us some goodies. I bet with the unlocked goodness ICS would scream on this phone, even with it's less-than-optimal amount of RAM.
I just want to personally thank you for everything you have done with this phone. I still use CM7 as my daily driver and love it despite the Wifi and the root issues and will continue to use it until I say F you to Motorola and get a different phone a little more dev friendly.
You are doing a great job keeping the DX2 afloat. If you can get ICS in this phone you'll have a very bright future ahead of you. I wish you the best of luck but I don't think you need it
I don't know anything about developing, modding or themes and I won't imagine how hard it must be to do what you have done for the DX2. For that and more: Thank You! Im sure we'll be happy to throw a dollar or two your way.. it's the least we can do. :good:
M-
question
you say no tegra2 has i c s
what about xoom?
was just asking in case that could give you done ideas
good luck DZK, keep killing it
I'm glad you came out with this post. I have had this phone since last summer like you and since then I have used both of your ROMs and have followed your work. Mainly because there are not very many developers still developing for this phone. Lol. I think a lot of people needed to hear this. you don't come in here that much and are not very active in the forums. Not that it's your fault or anything. we all know that you're busy. But people are used to regular updates. Even if they are just verbal ones. So when a dev takes their time and no one hears anything, they don't understand. Most of us in here explain your situation when someone comes in here asking about stuff. We are all grateful for what you have given us so far and the things that are coming down the road. Without you there would be no development for this phone. As much as everyone would like to believe, we all know you are not just some guy sitting behind a desk all day working for us. By the sound of it, it looks like school is going to be getting a lot more busy for you which means less updates for us. By the time you get around to developing again for this phone I may have moved on to another. Just want to say again. Thanks :good:
also just wanted to add that I'm surprised you felt the need to explain yourself, pretty stand up thing to do,
i would HOPE no one gives you guff for having a real life with , priorities, but then again this is x d a haha
this is something you do for fun, we all should realize that, and it's awesome that you have gotten as far as you have
keep plugging away bro (at real life)
ashclepdia said:
also just wanted to add that I'm surprised you felt the need to explain yourself, pretty stand up thing to do,
i would HOPE no one gives you guff for having a real life with , priorities, but then again this is x d a haha
this is something you do for fun, we all should realize that, and it's awesome that you have gotten as far as you have
keep plugging away bro (at real life)
Click to expand...
Click to collapse
I would think this is more for the newcomers here that don't know what's going on behind the scenes. Have you SEEN the kind of things people ask him on twitter? Lol
+1
ashclepdia said:
also just wanted to add that I'm surprised you felt the need to explain yourself, pretty stand up thing to do,
i would HOPE no one gives you guff for having a real life with , priorities, but then again this is x d a haha
this is something you do for fun, we all should realize that, and it's awesome that you have gotten as far as you have
keep plugging away bro (at real life)
Click to expand...
Click to collapse
Sent from my DROID X2 using xda app-developers app
I'm not a dev, but I am a project manager who works very closely with them, on very large scale deployments. Something that has always impressed me about you Bryan, is your prioritization and time management. Knowing where to focus energy in order to achieve maximum result, especially when strapped with limited resources, is a skill not as common as one might think--you've got it in spades.
I guarantee when you enter the work force, it's going to be something that sets you apart from a group of otherwise smart guys. Project managers and directors will LOVE you for that skill set.
That being said, thanks for giving us a portion of a sorely needed resource, it's appreciated.
DK you are the man! Thanks for everything!!! You and nitro saved the x2 without you two the x2 would be crap! Family is always first. Good luck with everything!
---------- Post added at 02:58 AM ---------- Previous post was at 02:54 AM ----------
ashclepdia said:
also just wanted to add that I'm surprised you felt the need to explain yourself, pretty stand up thing to do,
i would HOPE no one gives you guff for having a real life with , priorities, but then again this is x d a haha
this is something you do for fun, we all should realize that, and it's awesome that you have gotten as far as you have
keep plugging away bro (at real life)
Click to expand...
Click to collapse
+1000
Edit: I can't believe the asterisks...lol
**** whoever said what, ungrateful bastard!
Life first, just include Android in it
You are the miracle maker dragonzkiller, if anyone ever says less keep your head high and **** em...never a need to explain.
Keep doing what your doing, it rocks!!!
Ps sorry bout the language, it's a Jersey thing...lol
DROID DOES, Apple did...like I forgot when
I'm with the others, it's always nice to hear what's what, but you should never have felt it any kind of explanation was owed to us.
Even if you suddenly had to put it all to the side permanently, you'll always have my gratitude.
Droid X2 > Eclipse 2.2.1 > Tapatalk
Cheers DZK!! Thanks for your time which is not owed to anyone. Side projects are good esp. when going into difficult job fields. The distractions are going to be what keeps you going. Best of luck to you!
I do wonder now though if it makes more sense to continue to tweak CM7 than CM9.
jsgraphicart said:
I would think this is more for the newcomers here that don't know what's going on behind the scenes. Have you SEEN the kind of things people ask him on twitter? Lol
Click to expand...
Click to collapse
i don't think i HAVE seen what is said to him in twitter...Hope it ain't some crazy crap
Sent from my Galaxy Nexus using Tapatalk 2
Hey just want to stop in and say thanks for the work you do on this phone. And I agree with the what others have said you don't owe us anything we are just greatful with what ever time we can steal from you.
Sent from my Incredible 2 using xda app-developers app
Look, thanks every and as such. For those of you who think that I have to explain myself, I pretty much do. A lot of you guys know the basics behind what it is I'm dealing with, but don't KNOW. If that makes any sense. I really enjoy working on this device and working with the community. I know it seems like I might get snappy sometimes or I'm short with my answers, but please just keep in mind that I have a lot of things on my plate and that I mean well.
Someone pointed out that the XOOM is running a Tegra 2. I did forget that fact, however even with that being the case, it has helped us very little in our endeavors. In fact it's still on 2.6.35 if I remember correctly and the props are still designed with that in mind. However it is still an updated kernel to work with ICS and such still causes some problems.
DZK, man I appreciate all your efforts! I don' t have the plate you do to deal with but I can surely understand where you are coming from.
I do believe that the majority of the community appreciates tremendously what you do for us, and the ones that can't be patient and understand well they can just flip off!
Thanks man!
Dragonzkiller you have done so much for this community and our X2. Would you be interested in a 2 month old PERFECT condition Dinc2? At least you would get a phone with official ICS and it actually already does since UKB is using the official kernel from the China released OTA. Its a great phone with great battery life just a smaller screen. You have done so much for us I would be happy to hook you up with a great deal. One I won't be able to tell my wife about lol
DZK, I too am an engineering student currently, and I fully understand what you are/will be dealing with. Free time is something we engineering students don't have the luxury to afford
With that being said, I truly appreciate what you have done in the development of this phone and how much time you have devoted to doing so. Keep your head high and let the haters hate.
Travisdroidx2 said:
Dragonzkiller you have done so much for this community and our X2. Would you be interested in a 2 month old PERFECT condition Dinc2? At least you would get a phone with official ICS and it actually already does since UKB is using the official kernel from the China released OTA. Its a great phone with great battery life just a smaller screen. You have done so much for us I would be happy to hook you up with a great deal. One I won't be able to tell my wife about lol
Click to expand...
Click to collapse
HEY!!! I see what you're trying to do! Quit trying to kang our dev for the Dinc2 community!!!
Language warning! Don't open in front of boss or kids!
http://i.imgur.com/dWZMF.jpg

Outcry to the Community

Hello All,
In recent events we saw our primary kernel developer completely drop his project and leave. This is a sad thing, but it could have been prevented on both sides. It seems that there has lately been a huge misunderstanding of what working with a community means and what open source means, it is tearing the community as a whole apart.
I. USERS/TESTERS: (this is the part most of us know about)
This can roughly refer to anyone that is not a developer or submitting code, but it can also refer to developers using ROMs or Kernels produced by other developers. Anyone in this position needs to realize that almost ALL Roms/Kernels/Themes are experimental even if considered "stable". There is a reason that on both Rootzwiki and XDA it is common to see developers stating they are not responsible for any damage done to your device or your data.
Device problems will differ from one device to another due to security implementations or new code/hardware or even something else. It needs to be understood that a kernel/Rom release that has bugs may NOT be due to code written by the dev, but by an inherent flaw in the hardware OR the stock code.
What does this mean to you?
Well, in order to function as effectively as possible a general guideline should be followed.
Be Tactful - Lets face it, there are going to be issues with ROMs and Kernels. There will never be a truly 'stable' release. Try to report issues in a polite and friendly manner. If you disagree with a developer, you can let them know, just be sure to be as tactful as possible, also make sure to provide adequate reports and detail.
Detail, Detail, Detail - Many of the newer folks don't know how to access logfiles, but this shouldn't stop you from being detailed. When an issue is come across, make sure to include as much detail as possible. For clarification, ANYTHING that is changed from stock configuration should be considered. For kernels, it is good to include any and all adjustments you have made. If a log can be pulled, DO IT, it won't hurt and the developer has an easier time figuring it all out.
Try to learn - The development community is a big place. By learning, you verify that you can help other newbies down the line, and that you provide more assistance to developers.
II. Developers: (the part less of us know about)
Ah, developers, without all of you, we wouldn't exist. Someone needs to do the work, and you provide the dedication and time. Most of us can't thank you enough. However, it seems that recently a lot of the developers are developing for the wrong reasons and are doing things against the very ideals we all stand for.
When developing with a community, ALL developers sign a non-verbal social contract. This contract includes many things.
- You are going to deal with some harassment (can be mitigated by mods) - Some people have bad days, others are asshats.
- Younger members will take you for granted
- Younger members will have difficulty providing detail
- The community will expect support for your product(s)
- Other developers (mostly new developers) will not credit you for your work occasionally (can be mitigated by mods)
All these things and more should be expected when working with a community. As a developer, you need to accept ALL of these things in order to contribute to making the community a healthy place.
Eventually, a developer must leave a device and move forward for WHATEVER reason they choose. This is inevitable, but in order to provide a healthy development cycle a developer should ALWAYS provide their source code for a time after development has stopped. This way projects can live on with other developers or be forked entirely.
MY COMMENTS ON TODAY:
DSB9938 - You are a fantastic developer and I urge you not to leave. I do believe you are misguided in pulling all your code and preventing others from forking or continuing your work. It goes against all that open source is about. You signed the social contract and you couldn't handle the terms, you wronged the community by breaking the trust you had developed.
Dr_Drache - Seriously? Kicking me from the AndIRC #droid-dna chat because you don't agree with what I say here? Did I step on your ego much? Stopping your s-off development because of all of this as well? You are whats wrong with the developers side of the community. God forbid someone disagree's with you, you either kick them or pull your project entirely. Go develop for Microsoft or some other proprietary company. You have forgotten about what the community really means and what open source is about.
Everyone else - We can pull through this. I have already started researching to pick up kernel development. It will be slow since DSB refuses to assist, but it can certainly be done.
Mods - We can't afford to lose more developers. We have to stop the harassment.
I agree with your post except the parts directed to DSB and Drache because it is a continuation of the feud. Let's just wipe the slate clean and follow the other parts of your comments because they are good guidelines on how to interact with each other.
th3raid0r said:
Hello All,
In recent events we saw our primary kernel developer completely drop his project and leave. This is a sad thing, but it could have been prevented on both sides. It seems that there has lately been a huge misunderstanding of what working with a community means and what open source means, it is tearing the community as a whole apart.
I. USERS/TESTERS: (this is the part most of us know about)
This can roughly refer to anyone that is not a developer or submitting code, but it can also refer to developers using ROMs or Kernels produced by other developers. Anyone in this position needs to realize that almost ALL Roms/Kernels/Themes are experimental even if considered "stable". There is a reason that on both Rootzwiki and XDA it is common to see developers stating they are not responsible for any damage done to your device or your data.
Device problems will differ from one device to another due to security implementations or new code/hardware or even something else. It needs to be understood that a kernel/Rom release that has bugs may NOT be due to code written by the dev, but by an inherent flaw in the hardware OR the stock code.
What does this mean to you?
Well, in order to function as effectively as possible a general guideline should be followed.
Be Tactful - Lets face it, there are going to be issues with ROMs and Kernels. There will never be a truly 'stable' release. Try to report issues in a polite and friendly manner. If you disagree with a developer, you can let them know, just be sure to be as tactful as possible, also make sure to provide adequate reports and detail.
Detail, Detail, Detail - Many of the newer folks don't know how to access logfiles, but this shouldn't stop you from being detailed. When an issue is come across, make sure to include as much detail as possible. For clarification, ANYTHING that is changed from stock configuration should be considered. For kernels, it is good to include any and all adjustments you have made. If a log can be pulled, DO IT, it won't hurt and the developer has an easier time figuring it all out.
Try to learn - The development community is a big place. By learning, you verify that you can help other newbies down the line, and that you provide more assistance to developers.
II. Developers: (the part less of us know about)
Ah, developers, without all of you, we wouldn't exist. Someone needs to do the work, and you provide the dedication and time. Most of us can't thank you enough. However, it seems that recently a lot of the developers are developing for the wrong reasons and are doing things against the very ideals we all stand for.
When developing with a community, ALL developers sign a non-verbal social contract. This contract includes many things.
- You are going to deal with some harassment (can be mitigated by mods) - Some people have bad days, others are asshats.
- Younger members will take you for granted
- Younger members will have difficulty providing detail
- The community will expect support for your product(s)
- Other developers (mostly new developers) will not credit you for your work occasionally (can be mitigated by mods)
All these things and more should be expected when working with a community. As a developer, you need to accept ALL of these things in order to contribute to making the community a healthy place.
Eventually, a developer must leave a device and move forward for WHATEVER reason they choose. This is inevitable, but in order to provide a healthy development cycle a developer should ALWAYS provide their source code for a time after development has stopped. This way projects can live on with other developers or be forked entirely.
MY COMMENTS ON TODAY:
DSB9938 - You are a fantastic developer and I urge you not to leave. I do believe you are misguided in pulling all your code and preventing others from forking or continuing your work. It goes against all that open source is about. You signed the social contract and you couldn't handle the terms, you wronged the community by breaking the trust you had developed. If you do not return, I can only hope that other, BETTER developers (in skill and ideology) fill your shoes.
Dr_Drache - Seriously? Kicking me from the AndIRC #droid-dna chat because you don't agree with what I say here? Did I step on your ego much? Stopping your s-off development because of all of this as well? You are whats wrong with the developers side of the community. God forbid someone disagree's with you, you either kick them or pull your project entirely. Go develop for Microsoft or some other proprietary company. You have forgotten about what the community really means and what open source is about.
Everyone else - We can pull through this. I have already started researching to pick up kernel development. It will be slow since DSB refuses to assist, but it can certainly be done.
Mods - We can't afford to lose more developers. We have to stop the harassment.
Click to expand...
Click to collapse
you, "my friend" need to learn when to stop running your mouth. you spent nearly an hour pretending to care, yet saying dsb/devs should give more back, because we have a contract with the community.
you never stepped on my ego, you were banned for being a luke. you want to quote GPL to the devs and expect us to fall down for you.
I agree with your post except the parts directed to DSB and Drache because it is a continuation of the feud. Let's just wipe the slate clean and follow the other parts of your comments because they are good guidelines on how to interact with each other.
Click to expand...
Click to collapse
I do need to get access back to the #Droid-DNA chat, otherwise it is VERY difficult to even begin development.
dr_drache said:
you, "my friend" need to learn when to stop running your mouth. you spent nearly an hour pretending to care, yet saying dsb/devs should give more back, because we have a contract with the community.
you never stepped on my ego, you were banned for being a luke. you want to quote GPL to the devs and expect us to fall down for you.
Click to expand...
Click to collapse
No, that is your assumption. I never even once demanded for more. I feel that the actions that have been taken are one of the sloppiest examples of open source development. I am trying to be a reasonable voice. I am trying to keep development going despite our recent setbacks.
I think that at the very least, devs should provide the sources so that development may continue after they decide to leave. Otherwise we loose too much progress.
th3raid0r said:
When developing with a community, ALL developers sign a non-verbal social contract. This contract includes many things.
- You are going to deal with some harassment (can be mitigated by mods) - Some people have bad days, others are asshats.
- Younger members will take you for granted
- Younger members will have difficulty providing detail
- The community will expect support for your product(s)
- Other developers (mostly new developers) will not credit you for your work occasionally (can be mitigated by mods)
All these things and more should be expected when working with a community. As a developer, you need to accept ALL of these things in order to contribute to making the community a healthy place.
Eventually, a developer must leave a device and move forward for WHATEVER reason they choose. This is inevitable, but in order to provide a healthy development cycle a developer should ALWAYS provide their source code for a time after development has stopped. This way projects can live on with other developers or be forked entirely.
Click to expand...
Click to collapse
No, no no no no no no. No social contract, this is an at will thing, that most of us are not paid for. Some of us do it for a living, and also do it here for fun. We do this for FUN. We do this for our benefit (having fun). I can not be anymore honest, anything I do here, I do for my benefit (Brain exercise and fun). I enjoy Android. The day I no longer enjoy it, I will either leave for good, or take a break like I have in the past. We can leave the playground and go home at any time. In fact I encourage developers to do this from time to time, It helped me greatly.
We do get some *sshat harassment, no we don't have to deal with it. We can ignore it, take it to a mod, or take our cake and go home. I tend to confront it, bad habit of mine
Younger members will take us for granted, some times you have to turn the power off to wake them up, or let them sit a minute waiting for you to release something they want.
Support should be appreciated, but not expected. We have families, jobs, and some of use have a life outside of Android(not saying I do ).
Most people who steal work, are not developers. They are general *sshats, that is all.
th3raid0r said:
MY COMMENTS ON TODAY:
DSB9938 - You are a fantastic developer and I urge you not to leave. I do believe you are misguided in pulling all your code and preventing others from forking or continuing your work. It goes against all that open source is about. You signed the social contract and you couldn't handle the terms, you wronged the community by breaking the trust you had developed. If you do not return, I can only hope that other, BETTER developers (in skill and ideology) fill your shoes.
Dr_Drache - Seriously? Kicking me from the AndIRC #droid-dna chat because you don't agree with what I say here? Did I step on your ego much? Stopping your s-off development because of all of this as well? You are whats wrong with the developers side of the community. God forbid someone disagree's with you, you either kick them or pull your project entirely. Go develop for Microsoft or some other proprietary company. You have forgotten about what the community really means and what open source is about.
Click to expand...
Click to collapse
RE: DSB9939: Sorry but take your social contract somewhere else, it doesn't even make sense. He didn't sign, didn't verbally agree, wasn't paid, rarely got a pat on the back. This is the guy who is the reason you all have root/unlock, and you are breaking his balls. Yeah no Beaups and I are not the reason, we were just the way to a means.
RE: Dr_Drache: AndIRC is not part of XDA, we are separate and really what goes on there doesn't belong here. If you have an issue, take it to me, Zifnab, TheFuzz4 or DougPiston. It is a PRIVATE server, and people are welcome at operator discretion. We are allowed to limit it to like minded people, or even to just be grumpy and randomly remove people if we wish (we don't normally). If you want to talk about it, you know where it is, and how to get ahold of me.
Dude, we don't another thread about this lol. I'm not here to harp on this fact, but I'm glad I dumped my DNA while I still had the chance. For some extremely odd reason, people don't know how to act in HTC threads. I definitely don't miss all of this drama from when I had my Rezound.
Sent from my SCH-I605 using xda premium
th3raid0r said:
I do need to get access back to the #Droid-DNA chat, otherwise it is VERY difficult to even begin development.
Click to expand...
Click to collapse
Requesting the community to be civil and then throwing in some parting shots is not ideal. I don't know what went down with you guys over there but maybe you can speak with the powers that be and work out an amicable solution.
jcase said:
No, no no no no no no. No social contract, this is an at will thing, that most of us are not paid for. Some of us do it for a living, and also do it here for fun. We do this for FUN. We do this for our benefit (having fun). I can not be anymore honest, anything I do here, I do for my benefit (Brain exercise and fun). I enjoy Android. The day I no longer enjoy it, I will either leave for good, or take a break like I have in the past. We can leave the playground and go home at any time. In fact I encourage developers to do this from time to time, It helped me greatly.
We do get some *sshat harassment, no we don't have to deal with it. We can ignore it, take it to a mod, or take our cake and go home. I tend to confront it, bad habit of mine
Younger members will take us for granted, some times you have to turn the power off to wake them up, or let them sit a minute waiting for you to release something they want.
Support should be appreciated, but not expected. We have families, jobs, and some of use have a life outside of Android(not saying I do ).
Most people who steal work, are not developers. They are general *sshats, that is all.
RE: DSB9939: Sorry but take your social contract somewhere else, it doesn't even make sense. He didn't sign, didn't verbally agree, wasn't paid, rarely got a pat on the back. This is the guy who is the reason you all have root/unlock, and you are breaking his balls. Yeah no Beaups and I are not the reason, we were just the way to a means.
RE: Dr_Drache: AndIRC is not part of XDA, we are separate and really what goes on there doesn't belong here. If you have an issue, take it to me, Zifnab, TheFuzz4 or DougPiston. It is a PRIVATE server, and people are welcome at operator discretion. We are allowed to limit it to like minded people, or even to just be grumpy and randomly remove people if we wish (we don't normally). If you want to talk about it, you know where it is, and how to get ahold of me.
Click to expand...
Click to collapse
A social non-verbal contract is never an official thing.
In a most basic form it is the trade of safety/stability for a service when it comes to political science. They apply everywhere.
The reason we are no longer roaming nomads is due to social contracts.
I am not saying that this social contract is why you guys develop. It is the generalized community expectations. They are going to vary from member to member as well.
I understand Support is not expected, on your end, however it is essential to a successful project and furthermore it is essential to reputation. Reputation garners donations and therefore some developers incomes.
Most of my other points also follow this same logic.
A healthy community flourishes when these invisible expectations are met. Look at the GNex development for example and take note at what the successful projects are and how they got there.
I understand that DSB wasn't well appreciated. But the community opinion doesn't get better if he leaves in this way, I would argue that he broke a lot of trust that the community had in him. He could have still taken a break, but there are much more elegant ways to do so.
Sigh.
You want a contract? What does the guy on the other end get out of the contract?
I make the things I make so that I can run my phone how I want to run it. That's the only reason. I do not make them for you, or to look like some smart guy, or for my ego. I am the first to admit that I don't know a damned thing about coding. What I make takes hard hours of trial and error. Basically pounding on things till I slowly figure out how they work and bend them to do what I want.
And I do it for days on end. Till it works well enough for me to run on my phone. And I AM PICKY. I want it to be perfect. However, I also share what I make. I share it so that others who want to have their phone run the way I do, don't have to work so hard to get there.
Now comes the rub. There are billions of people in the world. And I bet if you put every phone next to every other phone, you would still not find two setup and/or used the same way. Because of that, I cannot test every possibility. When people come to me with something that doesn't work, do I just say no? Of course not. I made it. I feel responsible for it working correctly.
Now, having determined that I am not a coder, what do I do? First I go ask other people who are much smarter than I am. People like jcase, beaups, imoseyon, show-p1984. These are the real coders/android hackers in the world. They look at the code and actually know what it's doing. They don't have to try to arm wrestle with it to figure out what's wrong.
If that doesn't work, I beat on it. I look at logs. When you post those logs in my threads, there's a bunch of people who read them, not just me. And if I can figure it out, with what help is available, I fix it. If not, I say so. Half the time, what's in those logs is of no help, a quarter of the time, it's in there what happened, but it wasn't related. And lets not forget those logs are usually thousands of lines to read through.
Do I claim to be perfect? Hell no. But I do my best. And that's the very limit of what anybody else on the site has any particular right to ask me for. Nothing more. I try to let slide all of the little digs that people use when things don't work right. But over time it gets to you, ya know? And you guys only see the public stuff, in the threads. You don't see the PMs. And see the people who come online to the chat. You have no clue.
Now top that off with people twisting my words to insult me. I basically said that there are other reasons you can have problems with your phone. I did not say it wasn't my kernel, I said it wasn't in the logs. And I have this guy come in and say yeah, mine runs fine on stock. Seems our phones are only crap on your kernel. Now how did you honestly expect me to react?
I have asked this guy more than once to not run my kernel because he has these outbreaks. This was not the first one. And if you go look through his previous postings, you can see his doesn't only disrespect me, he has outright disrespected MODs as well. This makes me wonder why he was still around to bother me in the first place. But that's beside the point.
Now anybody who thinks I'm curt with others, go read the stuff I've had to put up with and see how long you can take it. I have no problems with people posting when they have an issue. And I can tell you right here and right now, my stuff isn't perfect. But when I tell you I can't find it, or fix it, that doesn't give you the right to flip out and go off on me. That means you go back a version and wait till I make a new one, or you go run something else. I even made a simple stock one for those with issues to run so they could have system write if they had issues.
I DO NOT MAKE ANYBODY RUN MY STUFF.
Now, having said all of that. Put yourself in my shoes and see how happy you would be.
D
.
orangechoochoo said:
Requesting the community to be civil and then throwing in some parting shots is not ideal.
Click to expand...
Click to collapse
Yeah, hindsight is 20/20.
It's early in the morning but after reading these threads that big bottle of Grey Goose is calling.
dsb9938 said:
You want a contract? What does the guy on the other end get out of the contract?
I make the things I make so that I can run my phone how I want to run it. That's the only reason. I do not make them for you, or to look like some smart guy, or for my ego. I am the first to admit that I don't know a damned thing about coding. What I make takes hard hours of trial and error. Basically pounding on things till I slowly figure out how they work and bend them to do what I want.
And I do it for days on end. Till it works well enough for me to run on my phone. And I AM PICKY. I want it to be perfect. However, I also share what I make. I share it so that others who want to have their phone run the way I do, don't have to work so hard to get there.
Now comes the rub. There are billions of people in the world. And I bet if you put every phone next to every other phone, you would still not find two setup and/or used the same way. Because of that, I cannot test every possibility. When people come to me with something that doesn't work, do I just say no? Of course not. I made it. I feel responsible for it working correctly.
Now, having determined that I am not a coder, what do I do? First I go ask other people who are much smarter than I am. People like jcase, beaups, imoseyon, show-p1984. These are the real coders/android hackers in the world. They look at the code and actually know what it's doing. They don't have to try to arm wrestle with it to figure out what's wrong.
If that doesn't work, I beat on it. I look at logs. When you post those logs in my threads, there's a bunch of people who read them, not just me. And if I can figure it out, with what help is available, I fix it. If not, I say so. Half the time, what's in those logs is of no help, a quarter of the time, it's in there what happened, but it wasn't related. And lets not forget those logs are usually thousands of lines to read through.
Do I claim to be perfect? Hell no. But I do my best. And that's the very limit of what anybody else on the site has any particular right to ask me for. Nothing more. I try to let slide all of the little digs that people use when things don't work right. But over time it gets to you, ya know? And you guys only see the public stuff, in the threads. You don't see the PMs. And see the people who come online to the chat. You have no clue.
Now top that off with people twisting my words to insult me. I basically said that there are other reasons you can have problems with your phone. I did not say it wasn't my kernel, I said it wasn't in the logs. And I have this guy come in and say yeah, mine runs fine on stock. Seems our phones are only crap on your kernel. Now how did you honestly expect me to react?
I have asked this guy more than once to not run my kernel because he has these outbreaks. This was not the first one. And if you go look through his previous postings, you can see his doesn't only disrespect me, he has outright disrespected MODs as well. This makes me wonder why he was still around to bother me in the first place. But that's beside the point.
Now anybody who thinks I'm curt with others, go read the stuff I've had to put up with and see how long you can take it. I have no problems with people posting when they have an issue. And I can tell you right here and right now, my stuff isn't perfect. But when I tell you I can't find it, or fix it, that doesn't give you the right to flip out and go off on me. That means you go back a version and wait till I make a new one, or you go run something else. I even made a simple stock one for those with issues to run so they could have system write if they had issues.
I DO NOT MAKE ANYBODY RUN MY STUFF.
Now, having said all of that. Put yourself in my shoes and see how happy you would be.
D
.
Click to expand...
Click to collapse
Hey, I totally understand all of that.
I have made some tweaks myself, but I don't publish them because I know they don't have much application outside of myself.
I do know where you are at, I work at a large legal software company as a QA Analyst. I KNOW the daily grind on this.
The harrasment won't always go away. Hell, i get it here in a large company. It can be mitigated by a few things. For example you can use a smaller community.
You don't have to deal with these things at all, but if you leave on such bad terms without a way for someone to pick up where you left off, it doesn't leave a good impression on the rest of the community.
The fact that you don't know code makes this all the more impressive. You are a fantastic problem solver, it shows, maybe we can find some way to lessen the blow for you and yet continue public development?
th3raid0r said:
A social non-verbal contract is never an official thing.
In a most basic form it is the trade of safety/stability for a service when it comes to political science. They apply everywhere.
The reason we are no longer roaming nomads is due to social contracts.
I am not saying that this social contract is why you guys develop. It is the generalized community expectations. They are going to vary from member to member as well.
I understand Support is not expected, on your end, however it is essential to a successful project and furthermore it is essential to reputation. Reputation garners donations and therefore some developers incomes.
Most of my other points also follow this same logic.
A healthy community flourishes when these invisible expectations are met. Look at the GNex development for example and take note at what the successful projects are and how they got there.
I understand that DSB wasn't well appreciated. But the community opinion doesn't get better if he leaves in this way, I would argue that he broke a lot of trust that the community had in him. He could have still taken a break, but there are much more elegant ways to do so.
Click to expand...
Click to collapse
You keep saying signed social contract. It is non-sense man. What you mean is expectations from non involved individuals.
Most developers get jack for donations, only people who get tons are either A) the attention begging people who release 100000 roms for 1000 devices that are nothing special, or B) ones who release something special, and then the donation spree is short and sweet. We don't do it for donations. DSB is not making much from donations on this device, he does it strictly for fun and people are making it NOT fun for him.
I fell into B) with the DNA. I will say I made ~$800 from donations on the DNA unlock, it is not the rule but an exception. I bought two used phones really cheap to develop on ($200 and $140, gave the $200 one away to another developer for free after I was done. $140 one I will give away as well at some point.), pizza dinner for my kids ($35, my personal reward), sent some for another developer (DSB, for his work and risks) and donated the rest to various charities. This is NOT A normal amount of donations. Don't fool yourself thinking most developers are making an income of any kind doing this.
GNex community flourished due to paid support from Google (AOSP), and open documentation. Two things we did not have.
*PS*
If you haven't been in our shoes, you shouldn't pretend to know, and you shouldn't complain about us.
solutions anyone?
dsb, jcase I have to side with you guys entirely. I love your work and I appreciate it completely. I am grateful for you guys, were it not for you guys and other people like you I would not get to 'OCD' on my droid all hours of the night like I do. I have learned much. I am a machinist in a shipyard, I can understand fine tuning and perfection in your work.
Unfortunately most of today's societal behaviors even in grown adults are dysfunctional at best. I have been on the internet since it's inception to the public eye and all I can say is that arguing and bickering that happens on the internet is absolutely ridiculous. I feel bad for you guys and embarrassed for the "others."
I have to agree with what works though. My daughter, when she was young would throw a temper tantrum and slam her bedroom door, so I removed the door.
orangechoochoo said:
Sigh.
Click to expand...
Click to collapse
+1
Sent from my Nexus 7 using xda app-developers app
orangechoochoo said:
It's early in the morning but after reading these threads that big bottle of Grey Goose is calling.
Click to expand...
Click to collapse
Its almost night here, and Jack Daniels is calling me, all after reading all that posts and some chating on IRC... Never ever see such outcome because of some not polite posts. I have degree in International Relations and first thing i 've learned - don't say what you think, say what you need to say and SMILE )))) We all just people. I got my family. Wife, kids... But i spend time here not only because of kernels, ROMs and all that stuff. But because of great community. It looks like that 1 person can spoil all that great atmosphere.... :silly:
jcase said:
You keep saying signed social contract. It is non-sense man. What you mean is expectations from non involved individuals.
Most developers get jack for donations, only people who get tons are either A) the attention begging people who release 100000 roms for 1000 devices that are nothing special, or B) ones who release something special, and then the donation spree is short and sweet. We don't do it for donations. DSB is not making much from donations on this device, he does it strictly for fun and people are making it NOT fun for him.
I fell into B) with the DNA. I will say I made ~$800 from donations on the DNA unlock, it is not the rule but an exception. I bought two used phones really cheap to develop on ($200 and $140, gave the $200 one away to another developer for free after I was done. $140 one I will give away as well at some point.), pizza dinner for my kids ($35, my personal reward), sent some for another developer (DSB, for his work and risks) and donated the rest to various charities. This is NOT A normal amount of donations. Don't fool yourself thinking most developers are making an income of any kind doing this.
GNex community flourished due to paid support from Google (AOSP), and open documentation. Two things we did not have.
*PS*
If you haven't been in our shoes, you shouldn't pretend to know, and you shouldn't complain about us.
Click to expand...
Click to collapse
Never said you make a living off the income generated from donations. I know it is mostly small, but the funds do help most people. It is also nice to know that you mean something to a few individuals.
Also, I work at a legal software company as a QA Analyst officially, but I do mostly QA Engineering work for no recognition, no additional pay, and the occasional bit of harassment when someone doesn't understand my methods. I really DO get the environment.
The only thing I am complaining about is devs leaving on such bad terms without a way for the community to recover, that's it.
th3raid0r said:
The only thing I am complaining about is devs leaving on such bad terms without a way for the community to recover, that's it.
Click to expand...
Click to collapse
What makes you think anybody owes "the community" a way to recover?
D
.

What can we do about the end of support and lack of official bootloader unlock?

I received the below e-mail today. I did not appreciate being contacted out of the blue via e-mail; if you feel the need to contact me, use XDA's tagging feature. With that said, I thought I'd reply in public with my thoughts on the matter, hoping to drive a constructive conversation about Verizon Wireless' restrictions for devices on their network. My initial response is in post 2.
Please, think through your responses before posting. Make sure they ADD to the conversation.
What do you think of having everyone from XDA and the CM community using the DINC 4G LTE file Better Business Bureau complaints against verizon? It made a business decision not to give us updates, and has deliberately removed the DINC 4g from the HTC Unlock program. They shouldn't be allowed to abandon the platform and to remove unlocking ability that was there.
BBB asks them to respond within 14 days. [edit: link removed]
or have you already tried this route?
Click to expand...
Click to collapse
I will leave it up to the writer of the e-mail if he/she would like to make himself/herself known here.
Can you point to a single advertisement by either HTC or Verizon that the Droid Incredible 4G LTE would ever be included in HTCDev's unlocked bootloader program? Even HTC's generic advertisements include disclaimers that some devices may not be included due to various restrictions (the most obvious being carrier refusal). HTC can justify the ability to unlock the bootloader pre-public availability as a means to let developers directly related to software development and quality assurance alter the ROM before release. To a handful of end users who get the device in the early days of release, they get to sneak in and use the unlocker under the "Other devices" category of the program. I suspect we owe HTC a thank you for dragging their feet for a week before disabling the unlock ability for this (and several other) device(s). There is no legitimate complaint that can be filed towards Verizon concerning this matter since they never advertised this as an available feature.
On the topic of abandoning the platform, software-wise, the last available software update for the Incredible 4G still works with reasonable stability and all advertised features are enabled. It is natural for technology devices to age and need replacement; a balance has to be struck between user content or disdain and extent of support. Verizon has apparently deemed there will be very little blowback by prematurely ending software updates. Considering the number of users I see in the XDA forum section for this phone, I'd guess they're right. About the only sticking point that could be leveraged to force a software update out of Verizon is if there are security vulnerabilities that are either being actively exploited or pose a real threat of being exploited in the near future.
Succinctly, we are at the mercy of Verizon's "generosity" concerning extended functionality of, and software updates for, the phones on their network. With these thoughts, I believe we can only ask them to help us out... with reason, anger, begging, or whatever tactic you find most influential. I don't think we can force their hand.
Your thoughts XDAers?
I agree with mdmower. Having come from the OG Droid, I had zero expectation for HTC or Verizon to let me unlock the phone. While I did not expect this phone to be the left-handed, red-haired step-child twice removed orphan of Verizon, it is a great phone with a 4" screen. The size is good (still prefer OG Droid) and the processor and internet speeds are great. I personally am quite content with this phone. We have been blessed with some extremely talented developers and supporters who have
Developed a method to unlock despite HTC/Verizon
Developed two methods for s-off:
DirtyRacun - IMHO, unlimited.io did a great job
FacePalm - Haven't tried, but looks great
Two great recoveries:
Official CWM Recovery, Plus PhilZ
TWRP Recovery
Developed an Incredible Rock Solid Sense ROM in ViperLTE
Developed a solid, official CyanogenMod ROM .
There are probably more, but those are just off of the top of my head. I am also still seeing great ongoing development work for ROMs for this phone. Sure, this phone doesn't have the plethora of ROMs that the OG Droid, Dinc2, Rezound, or [insert model here], but what we do have is solid.
I'm not exactly sure what Verizon owes us. We have a great phone with a great 4GLTE network (at least in my area). It should also be noted that Verizon actually put out an OTA for the OG Dinc around 2+ years after its release with "Improvements and fixes". I would expect the same for this phone as well. I too believe that threats, anger, etc. will not do anything more than generate ill will.
Just my $0.03.
P.S. Why do we still care if there is an "official" bootloader unlock? As mentioned above, we have a proved method to unlock bootloader and/or gain s-off. Even HTC's site says that unlocking bootloader through their "official" site may void your warranty.
HTC Dev said:
Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader. HTC bears no responsibility if your device is no longer usable afterwards.
Click to expand...
Click to collapse
The only thing to take away from this is to avoid Verizon and HTC. They may not owe us anything more than we received, but they are clearly sub-par companies compared to others. Unfortunately, I can't ditch Verizon just now because I'm on a shared plan, but I will never buy an HTC phone again.
junkmail9 said:
I agree with mdmower. Having come from the OG Droid, I had zero expectation for HTC or Verizon to let me unlock the phone....
P.S. Why do we still care if there is an "official" bootloader unlock?
Click to expand...
Click to collapse
Just to clarify, I'm not content with the support Verizon has offered for this phone, I just realize that we cannot expect them to continue support. I am still not sure about the best avenues of communication with Verizon Wireless, so in a feeble attempt to get their attention, I write a short #openletter on G+.
A far as the official bootloader unlock, it is a little important. An example is the recently advertised CM installer (by the way, I do not have any insider knowledge about CM Inc.). The installer will almost surely be available only to devices with legitimate unlock ability. While the fireball is pretty much "a bit"-out-of-luck even if it did get official unlock, due to the inability to flash the boot partition while in recovery, at some point users need to convince Verizon Wireless to allow unlocked bootloaders for phones on their network. This is especially relevant to the many, many users who are wise enough to not tinker with their phones because of lack of knowledge. They deserve the opportunity to safely replace the legacy operating system on their phone, and this will only be possible if the carrier and manufacturer allow it.
The open letter seems pointless, besides maybe allowing other people to see and take note that Verizon ignores certain customers. As far as our phone though, no point really. Anyone you reach through G+, Facebook, Twitter, Verizon's customer service contacts, etc. will have no real power to do anything. They just give the typical "sorry, we're doing our best" garbage. The message never reaches anyone important enough to actually do anything. The only way a message may get to them is if the user base is very large, but even if we all wrote to them everyday it wouldn't help. Not enough people for them to care. As you said, we're at their mercy. Just have to wait.
mdmower said:
A far as the official bootloader unlock, it is a little important. An example is the recently advertised CM installer (by the way, I do not have any insider knowledge about CM Inc.). The installer will almost surely be available only to devices with legitimate unlock ability. While the fireball is pretty much "a bit"-out-of-luck even if it did get official unlock, due to the inability to flash the boot partition while in recovery, at some point users need to convince Verizon Wireless to allow unlocked bootloaders for phones on their network. This is especially relevant to the many, many users who are wise enough to not tinker with their phones because of lack of knowledge. They deserve the opportunity to safely replace the legacy operating system on their phone, and this will only be possible if the carrier and manufacturer allow it.
Click to expand...
Click to collapse
This is an excellent point I had not considered. I was not thinking about the larger issue, (nor am I savvy with the upcoming CM installer). Unfortunately, I have run into a few companies that have seriously dummied down their products because, as one tech support person told me, "some users may have a problem with the advanced features so we removed them." While I can try and understand that point, it was really frustrating because some advanced features I had come to rely on were removed in the product upgrade. Simply because some people could not comprehend how to use it properly? Is Verizon trying to protect us from ourselves, dummy down the phones for "the uneducated masses," or simply trying to force their customers to live with Verizon-installed bloatware?
Okay I have My own say to this.!
Okay so I left AT&T network when I owned the HTC Inspire 4g and moved on to Verizon because there service was better in my area and I purchased the HTC Droid Incredible 4G LTE as my first phone with Verizon, I came to like the phone because it was fast, snappy, and good on battery....... But I constantly waited for update to jellybean ( Sense 4+ ) which in reality would make the device more efficient and smoother than it was on Ice Cream Sandwich... And finally I heard the news that we were going to get an update to jellybean in the beginning of 2013.. But after so much time of waiting I finally gave up hope and said ***k the device and went back to AT&T...... and bought the HTC One XL because it recieved updates to sense 5. The device is like an older sibling to the inc4g with close to the same specs. I sold the Incredible 4g because I hated the lack of support for this device... The only good thing going for it was CM10 and the amazing sense kernel. This community deserves more than what has been given to them so far... So my question is why Verizon drop support for us.???? If this community received jelly bean j defiantly would sell my XL and come back to this community......
This is my only my concern.
Sincerely,
24ky
Sent from my HTC One XL using XDA Premium 4 mobile app
Here is a weird thought. let your money do the talking. leave Verizon. if enough of us leave we dont need to "change their minds". i brought this up in an HTC elevate detection not to long ago ( also how come htc bent over backwards because verizon wanted the bootload unlock for the ONE removed). instead of open letters or angry tweets and emails, just take your money to someone that appreciates you as a customer? put your money into a company that understands the development community and is willing to support you. how do you think verizon got so good? the used to listen to their customers. now that they are self sustaining they dont need to listen to us anymore. but i bet if their wallet was hit the would. they would bring back unlimited data, remove the block of google wallet, ect....
You wouldn't take your car to a mechanic that does great work but also makes you spend $$ money on things that don't need to be fixed.
my $.02
synisterwolf said:
Here is a weird thought. let your money do the talking. leave Verizon. if enough of us leave we dont need to "change their minds" i brought this up in an HTC elevate detection not to long ago. instead of open letters or angry tweets, just take your money to someone that appreciates you as a customer? put your money into a company that understands the development community and is willing to support you.
You wouldn't take your car to a mechanic that does great work but also makes you spend $$ money on things that don't need to be fixed.
my $.02
Click to expand...
Click to collapse
This is my point from before. This is the only thing you can really do. I wish I could dump Verizon right now, but I can't. For now I'll just settle for never buying HTC again.
somerandomname1 said:
This is my point from before. This is the only thing you can really do. I wish I could dump Verizon right now, but I can't. For now I'll just settle for never buying HTC again.
Click to expand...
Click to collapse
this too. maybe if HTC where to step in and help us it would be different.
OP not trying to troll or anything or start a war. i just wanted to get that out their. we do have an option to take our money somewhere else. or at least when this contract is over. ive said it before, i need unlimited data. i dont have wifi anywhere i work and im barely at home so if i have to give up my data plan i will give up my business too. im going to miss there unbeatable coverage but i cant stand to be hit in the balls over and over again with a smile on their face. :/
mdmower said:
I received the below e-mail today. I did not appreciate being contacted out of the blue via e-mail; if you feel the need to contact me, use XDA's tagging feature. With that said, I thought I'd reply in public with my thoughts on the matter, hoping to drive a constructive conversation about Verizon Wireless' restrictions for devices on their network. My initial response is in post 2.
Please, think through your responses before posting. Make sure they ADD to the conversation.
I will leave it up to the writer of the e-mail if he/she would like to make himself/herself known here.
Click to expand...
Click to collapse
My 2 cents on this from bitter experience. You will get zilch. You will waste precious amounts of your life trying hard to convince a rigid management who can care so little they'd be happy to break your phone to pieces and hand you another from their stockpile of dinc4g's just to get rid of them ASAP. I've gone through the whole lot with BBB complaints etc. for the Droid X2 by Motorola. haha, wasted my life there. And the countless pleadings to release the ICS ROM that HTC clearly developed for the Dinc2 (Incredible S, international variant got the ICS update) only to get on the Verizon chopping block and get its head unceremoniously severed, taught me one thing and that is we as consumers have knowingly chosen this path, that will give us limited to no flexibility on customization to stay on VZW and we have to "deal" with it.
With all good intentions, I request all to keep your expectations rock bottom. You have better chances of going to the moon on a future Russian spacecraft than convincing Verizon as to why this may be a good idea.
Sincerely,
A disgruntled Droidâ„¢ user.
here has been my android experience. started on og inc oct 2010 first droid phone considered ''high-end'' at the time (8 mp camera saaaaay whaaaat??!) then dinc2 great phone but compared to the galaxy S II and the galaxy nexus at the time it was a ''mid range" phone. now with the inc4g it is very ''mid range'' compared to what is out now. the galaxy notes and s4's and the 50 different htc One(s). if you want many different roms to flash to fix your ''addiction'' go nexus or one of the mainstream phones. you will find 100 different "Unofficial CM10.X" roms with "user tweaks" and "kernel tweaks" that in all actuality are nothing more then a reposync from source. yeah they might have a few different mods but they are usually so similar that you will not/could not tell the difference. like someone mentioned earlier I would rather have a few solid roms. a good sense (viper) or if you're an aosp guy like me there's cm. I think anybody who saw the specs of this phone (incredible 4g) and thought, "hey this is going to be the next BIG THING." I'm sorry to tell you that you were mistaken. xda dev support of a phone is only as good as the devs that own the device, and in our case we have a very small amount of active devs.
So I am the a-hole that emailed mdmower. I apologize profusely. When I saw your first post, I almost slunk away in shame, never to show my face here again. I am not even being a little bit facetious. You do great work for a community of people and I abused (what obviously is) an important rule. And I'm really sorry.
In an attempt to redeem myself just a little bit, let me point out one thing that you might not know:
mdmower said:
Can you point to a single advertisement by either HTC or Verizon that the Droid Incredible 4G LTE would ever be included in HTCDev's unlocked bootloader program? Even HTC's generic advertisements include disclaimers that some devices may not be included due to various restrictions (the most obvious being carrier refusal) [SNIP] There is no legitimate complaint that can be filed towards Verizon concerning this matter since they never advertised this as an available feature.
Click to expand...
Click to collapse
Actually, some states may have more favorable law here. First and foremost, many states have an unfair/deceptive business practices law that are distinct from the false advertising law. Example: New York has GBL Section 349 (trade practices), and 350 (Advertising). These are consumer-oriented statutes and so they have some bite.
On this point, while Verizon has never said they would provide us with Jelly Bean, there are some nice facts here like how many people were locked into 2 year contracts on a phone that Verizon stopped updating during their two year period. I've seen suggestions that Verizon is pulling this with older phones in order to force upgrades, and if true, that would be the basis for a claim. But here, I think the HTCDev unlock is actually pretty damning. We should be entitled to take discovery into the real reasons why Verizon forced HTC to remove the phone from the program. Given the repeated warnings about waiver of warranty, and the presence of other VZW phones in the program, it's hard to believe it's a support issue.
Finally -- of note is that the ACLU has filed an FTC complaint on this subject earlier this year. Unfortunately I cannot post the link since I just registered for this post (long time lurker) but it's the 2nd hit for "april FTC complaint android" (see pages 6-9) Their basis is the potential for security flaws which go unfixed. The relief they are requesting is pretty broad. I'm actually surprised that there haven't been follow-on civil suits already.
Anyway, I am really sorry again. I'm going to crawl back under the rock I came from now.
If it's any comfort: my punishment is that my D4INC is a flicker model.
PrimePalaver said:
If it's any comfort: my punishment is that my D4INC is a flicker model.
Click to expand...
Click to collapse
Haha burn! Just kidding... it's cool.

[Q] Bootloader?

So this may be a stupid question, and I know that the HDX bootloader is essentially a tank, but in other cases I know some devices have gotten lucky by chainloading u-boot to load custom kernels and such. Is this possible in our instance, or am I totally off-base and missing something? I mean I'm assuming I am wrong as noone has mentioned it yet, but I'm just curious as to why.
S_transform said:
So this may be a stupid question, and I know that the HDX bootloader is essentially a tank, but in other cases I know some devices have gotten lucky by chainloading u-boot to load custom kernels and such. Is this possible in our instance, or am I totally off-base and missing something? I mean I'm assuming I am wrong as noone has mentioned it yet, but I'm just curious as to why.
Click to expand...
Click to collapse
No, the issue here is, most of the guys that have low level Qualcomm experience are not here. We, aside from maybe Hashcode, are mostly adventurous hackers & tweakers. Don't get me wrong, Cpajuste has made some big strides & I've saved a ton of bricks, but for me it's mostly because I've been around XDA since 2002 or 2003. In fact, I used to have a username for every platform, the last being 2006 when XDA started say only one account per person, which was my new WM6 account.
At any rate, we are limited because of a few reasons, such as the HDX is not really a device available worldwide. That knocks a lot of potential developers out of the equation. The second issue is that it's not mainstream Android. It is a fork viewed as inferior by most, regardless of how much better the hardware is. The HDX is also still a fairly new device, particularly when you consider the LTE models just started shipping mid-December.
So, sure it can & probably will even happen, but just look how long it took to fully unlock the Verizon Note 2 bootloader or especially some of the 2012 Moto devices. Nearly a year? Maybe more for some?
GSLEON3 said:
No, the issue here is, most of the guys that have low level Qualcomm experience are not here. We, aside from maybe Hashcode, are mostly adventurous hackers & tweakers. Don't get me wrong, Cpajuste has made some big strides & I've saved a ton of bricks, but for me it's mostly because I've been around XDA since 2002 or 2003. In fact, I used to have a username for every platform, the last being 2006 when XDA started say only one account per person, which was my new WM6 account.
At any rate, we are limited because of a few reasons, such as the HDX is not really a device available worldwide. That knocks a lot of potential developers out of the equation. The second issue is that it's not mainstream Android. It is a fork viewed as inferior by most, regardless of how much better the hardware is. The HDX is also still a fairly new device, particularly when you consider the LTE models just started shipping mid-December.
So, sure it can & probably will even happen, but just look how long it took to fully unlock the Verizon Note 2 bootloader or especially some of the 2012 Moto devices. Nearly a year? Maybe more for some?
Click to expand...
Click to collapse
Thanks for the response, this makes a lot of sense. Its like I understand in my head its probably going to take a long time if ever, I'm just not wired to be particularly patient.

Categories

Resources