Related
Reposted with permission:
http://forum.xda-developers.com/showthread.php?t=1419815
OPERATION: Make Our Selves Heard (#OPMOSH)
DISCLAIMER:
We here, in the movement of #OPMOSH do not consider this spam, we do not consider this slandering Moto, we simply use this as a method of having our concerns heard. Motorola Mobility Inc. has been a powerful company that has been around for a very long time, and one we hope to see long in the future as well, before and after the Google buyout.
About this movement:
Motorola Mobility Inc. has become famous for its lies, slanderous ways, and tendency to flat out prove time and time again that it cares not for its customers after they walk out of that store with their Motorola-branded device. Since the early days of Android, post Droid 1, we have sat down and took our locked bootloaders like a man. There came to be a boiling point - and a full-out war was launched on their social media sites. Sound familiar? The same thing that worked with HTC and now with Asus. We received a generic "second half of 2011" timing. Guess what! It's now Q1 2012, and not only have they missed their deadline, but they have IGNORED all bootloader-related questions, given NO official announcement of their plans still being in motion, and thus must have forgotten that we are a core, dedicated community that wishes nothing more than to enjoy the phones we were given. Let's make ourselves heard yet again, turn the heat up, and make Moto (like HTC) get off of their asses and DO SOMETHING. Everyone counts!
Moto's Facebook - Moto's Twitter - Petition - FCC Complaints (Against Verizon)
So....What can I do?
FIRST OFF, SIGN THE PETITION:
This is included in the email, so it is crucial that it continues to grow in number.
Then....
TRY CALLING VERIZON'S EXECUTIVES.
Make sure before calling that you are very informed about the issue and confident in your position, yet can be quite calm. Do not show any disrespect towards Marie H or the person you call. They are merely the (wo)man-in-the-middle, and you simply need to explain to them your position and back it up with facts. Also, do note that all times are EST.
Call Marie H. at (412) 266-7756 on Monday - Fridays, 8 am to 5 pm. OR Michelle at (803) 231-1787 on Monday - Fridays, 7 am to 4 pm. OR Call Verizon customer service at *611 or (800) 922-0204 and get to a rep by mashing 0.
This is something you cannot copy-paste, unfortunately. Here are some guidelines that should help you be successful in your endeavor:
- First off, if you get the voicemail, leave your name, number, and a time you can be contacted in case they wish to follow-up call.
- Mention that many are filing FCC complaints because this violates Block C guidelines. (Do research in case this is brought into question)
- Mention that HTC, Motorola, and Samsung have bootloader-unlockable devices on the network right now; (HTC has their 2011 devices, Moto has the Xoom, and Samsung the Galaxy Nexus)
- Mention that the bootloader being locked does not allow the device to do anything that a laptop that is using a 4G hotspot cannot do even faster/more efficiently, including hogging network resources.
- Mention that the bootloaders being FORCE locked (as in, not unlockable) does not offer protection from any present viruses or attacks of Android devices.
- Mention also that unlocking the bootloaders could very well use a system like HTC uses - which stores the IMEI of the device and voids its software warranty indefinitely, making Verizon's warranty services not liable for what a user installs on their device.
- Close your talk/voicemail by stating the number of signatures on the petition, currently well over 2,500, and saying that this is a widespread concern of many users, that wish Android to be truly open.
- Say thank you before you hang up, it'll really give off a good impression.
TRY AN FCC COMPLAINT:
http://esupport.fcc.gov/complaints.htm
Select Wireless Telephone > Billing, Service, Privacy, Number Portability and other issues > Online Form. Fill out your information, scroll down, fill out 1 and 2, skip 3 and 4. Then in 5:
- Tell the FCC that your phone’s bootloader was sold to you locked, preventing the regulatory requirement of BLOCK C Devices (MAKE SURE TO MENTION BLOCK C!!!) that "Consumers should be able to download and utilize any software applications, content, or services they desire" - make sure to cite that.
- Also helpful would be dispelling the "Reasonable network management" exclusion. Tell the FCC that Verizon allows tethering of unauthorized devices to 4G LTE services through their mobile hotspots and their paid phone tethering functionality as-is, ones that are more bandwidth-hungry and also permit installing custom operating systems, and have a potential of doing significantly more damage, such as laptops.
If you don't want to write yours up manually, we will have a pre-made step 5 that you can just copy paste soon, hopefully.
TRY EMAILING:
TO: [email protected], [email protected], [email protected], [email protected]rola.com, [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
To Whom It May Concern,
The independent communities that you catered to with your announcement earlier last year are very very excited for your bootloader unlock solution. However, the "second half" of 2011 has come and gone quietly; why is it that the public has received no notice that the bootloader unlock solution is still in works? A small-scale petition has made its rounds about the Android community, and has already gained over 2,500 signatures just under 55 hours after being made public: http://www.change.org/petitions/motorola-mobility-inc-unlock-all-smartphone-bootloaders-2
Clearly, the demand is indeed still quite strong (as can be seen on your social media networks, Facebook and Twitter), and it would be quite reassuring to the communities that not only pay for your devices every upgrade opportunity, but also help develop the Android operating system that you are using on the aforementioned devices, to have an announcement that the bootloader unlock/relock solution is still on track for a timely release. This would also potentially double as reassurance to on-the-fence Galaxy Nexus/HTC smartphone buyers to go with the Motorola Droid RAZR, with its KEVLAR backing, Verizon 4G LTE speed, powerful 1.2 GHz dual core processor, and new bootloader unlock/relock solution instead. Thank you for your time, and I look forward to your response.
Sincerely,
A Motorola Mobility Enthusiast.
TRY TWEETING:
@Motorola - How about those unlocked bootloaders you promised second half of 2011? @HTC cares, do you? http://moto.ly/icsboot
TRY POSTING ON THEIR FACEBOOK WALL:
@Motorola - I'm a faithful Motorola customer, and I'm starting to have second thoughts. Honor what Android stands for, openness, and give us the bootloader unlock tool that you promised "second-half of 2011". http://moto.ly/icsboot #OPMOSH
MAKE SURE TO SIGN THE PETITION!!
It is the backbone of this movement. We need as many signatures as possible.
We NEED to be heard to get anywhere. Spread the word to your Facebook friends, your Twitter friends, your Google Talk friends, your favorite Android news site... Spread the word! Bring freedom to the Android ecosystem, like Andy Rubin and Rich Miner intended.
Thank you SO much for your support. This community is amazing and I know our endeavors will be successful. See you on Moto's Facebook!
In an effort to get better coverage, I would suggest crossposting to as many Android forums outside XDA as possible. Most definitely, send it to Android Police. It could be worth a shot. While I understand different folks have preferences as to what forums they frequent, getting the word out is paramount.
Just my $0.02 US
Make sure you start a similar one with verizon because i am pretty sure motorola is going to play the blame game as soon as this gains momentum based on the line from the blog post
"where operator and channel partners will allow it. "
I'd like to think this will work if we get it out there enough. It's the customers vs. the company, I can't think of anybody who would want it stay locked except for those people who are like "oh but then it'll just be easier for people to screw up."
zeb carter said:
In an effort to get better coverage, I would suggest crossposting to as many Android forums outside XDA as possible. Most definitely, send it to Android Police. It could be worth a shot. While I understand different folks have preferences as to what forums they frequent, getting the word out is paramount.
Just my $0.02 US
Click to expand...
Click to collapse
couldnt he also post it to many of the xda motorola forums? except those that are already unlocked of course
id send it to droid-life as well
Sent from my DROID X2 using xda premium
This is a good idea. I like the idea of mass emailing them.
Sent from my DROID X2 using XDA App
I'll be doing my part as well. Thanks for starting this thread.
ztotherad said:
couldnt he also post it to many of the xda motorola forums? except those that are already unlocked of course
id send it to droid-life as well
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
I'd even post on the unlocked ones. Many people would help the cause. They could write how much they benefit from their phone with an unlocked bootloader. I even bet a significant number of the larger Android community would assist because we all have the same end game in mind.
This thread is great. I was just thinking yesterday of collecting the various resources to petition Motorola. You made everything very clear and we thank you. SPREAD THE WORD!! and, most importantly, ACT ON IT PEOPLE!!
Now we need a script to auto-tweet, auto-email, and auto-flame Motorola AND Verizon.
I'll help out with this cause any way that I can. I just posted on Moto's Facebook Page.
Sent from my DROID X2 using xda premium
i just sent out an email to the addresses that were listed by the OP, lets see how long they can ignore the emails from the customers and ignore the petition. I hope they don't send back a generic email that states that they're "working" on it. If the dx2 is a "closet" device then maybe we can gain at least the key to unlock and we'd be gaining our pudding.
Being a recent HTC convert and former X2 owner, I can say that this could really work. We got our Rezound unlocked. This needs to get out there. You'd be surprised how powerful this can be if enough people here on XDA start making noise. Thanks, OP, for posting this. Good luck!
Can we organize a time to CALL motorola? I think clogging up their phone lines for a couple of hours may be more effective than jamming their inboxes with easily deleted emails. If we could get even 100 people to just call at the same time, we could be HIGHLY effective.
We could all also call the phone number listed in post number 96 of the similar thread in the RAZR forum. I think that if we politely annoy enough people things can get better.
'Bout to hit 1000..
Guys thus could work.we doubled our sigs in less then twelve hours at this rate we'd have 5000 by Saturday. Remember to send them emails and to remind other moto forums!! I have a feeling that they just might listen if we bagger them enough.
Sent from my eclipsed Droid x2
antp121 said:
Guys thus could work.we doubled our sigs in less then twelve hours at this rate we'd have 5000 by Saturday. Remember to send them emails and to remind other moto forums!! I have a feeling that they just might listen if we bagger them enough.
Sent from my eclipsed Droid x2
Click to expand...
Click to collapse
I signed the petition.
I posted in the Motorola X2 forums that HTC has already unlocked their bootloaders within the United States, and that the X2 will be my last Motorola phone if they do not go through with their statement they released to unlock the bootloaders.
I sent an email (not nasty, but to-the-point) in the same vein as my post in their forums.
Remember, people. Do NOT be nasty about it: no name calling, no cursing, etc. Just state that you feel they should unlock the bootloader, especially since HTC has done it. I went as far as to suggest they contact HTC to see how they got Verizon and AT&T to allow this. Then, state that you won't be purchasing any more Motorola phones if they do not move forward with this. I was being kinder and stated that we, as customers, deserve an answer from them one way or another (whether they will unlock the phones or not). If they choose not to unlock the phones nor give an answer, the X2 was going to be my last Motorola phone.
It wasn't nasty, it was to the point and it was with tact. That's what we need, not a lot of flaming, etc. That won't get you anywhere and they'll just ignore it and treat it as if it were from some child or teenager, which is what I would do with it as well.
BTW, just read this excellent article on Droid Life. Pretty damning against Motorola if you ask me!
http://www.droid-life.com/2012/01/0...eed&utm_campaign=Feed:+DroidLife+(droid+life)
I went ahead and updated my post in the Moto forums to include this article link as well.
BTW, this has to be the 3rd or 4th "article" I've seen today about this. I think it's picking up steam. Now, whether Moto decides to listen and take action is another thing.
Exactly we must be to the point but not to forward it could be offensive plus that could hurt the cause And we still need a little more signer so tell your friends mom etc
Signed petition.hope were heard.
antp121 said:
Exactly we must be to the point but not to forward it could be offensive plus that could hurt the cause And we still need a little more signer so tell your friends mom etc
Click to expand...
Click to collapse
I went and called Mrs. Ellen and Mrs. Houtz. They both want to help and are ready to join our cause. Let's make moves people.
Sent from my DROID X2 using xda mid-grade
Posted it on a google discussion in another forum. Can we get a list of forums this has been posted on?
I believe that we should have this posted on every phones forum because it's not just for us that it will benefit but it would benefit everyone and for me I wouldn't have to wait on a phone to see if it's dev friendly or just another red headed step child.
Sent from my DROID X2 using XDA App
Hi all!
I sent DJ_Steve money for coffee a while ago, and I was hoping he would get us a nice ICS build for our devices. I still hope him to do so, but I want to ask two related questions here:
How many of you Streak 5 owners would chip in, say... 5 or 10 USDs to get us an ICS upgrade?
And for you skilled developers out there: how much money and kudos would you think would be necessary for you to continue the development?
I have two of these beasts. I really enjoy the user experience, and I don't want to have to buy a new device in a while. I would gladly put down another 5 or 10 bucks to see this happen.
Would you?
Cheers!
I'd already donated to djsteve when he got gingerbread out so I'd be down for another 20 bucks.
ye id sling him a 20
I would gladly donate 20 dollars to the developer who makes a working ICS port and disables the capacitive buttons.
Pledges like this have gone around and around for the last 6 months....
AFAIK ICS wont make it to the Dell Streak 5 any time soon because the drivers still need to be reverse engineered to make it work.
Unless Dell release the drivers ICS on the 5 wont happen
ashr said:
Pledges like this have gone around and around for the last 6 months....
AFAIK ICS wont make it to the Dell Streak 5 any time soon because the drivers still need to be reverse engineered to make it work.
Unless Dell release the drivers ICS on the 5 wont happen
Click to expand...
Click to collapse
Ashr is on target (straight from DJ_Steve's twitter to this thread), unless there is somebody out there with lots of time on their hands to crunch code, not going to happen. Plus Steve said the other day he is getting close to the boiling point, because too many people are bugging him, that he might just stop ICS development all together. Good thought and all that, but think it is a bridge too far to see ICS on Dell Streak 5 and the fault clearly falls on Dell's shoulders. Dell could have released the code a long time ago, but chose’s not too and hides behind very weak excuses. Other companies have released their source code and very good ROMs are the result of it.
Is there an easy way to publicly ask Dell to provide all the necessary tools and code to allow the devs to get us an ICS for our Streaks?
The way I see it, Dell looses nothing by providing with such tools, and although indirectly continue to support the device which is a good thing. Not doing it doesn't make much sense, and I'd see it as *bad business policy*.
Obviously you hadn't seen the press release from Dell where they slammed their Android devices because of their unrealistic expectations regarding Android as well as their lack of any marketing whatsoever.
Dell doesn't care about "bad business policy" regarding Android, and even if they did there's nothing they can do about it. Reason why is they didn't develop the Streak. It was developed for them and the company that did the developing has shown absolutely zero interest in releasing the sources for their drivers. Sorry, but the only way the Streak is going to see ICS is if the drivers are reverse engineered.
It's really dell's job to get the whole driver source mess sorted out.
While Qisda did build the hardware and make the rom, they did it on contract for dell. Even if they wanted to they couldnt do it without dell's blessing.
It's the equivilent of flying on a plane, if your service was bad, something went wrong, plane crashed; you dont contact/blame boeing/airbus, you blame the carrier. Even if it was boeing/airbus's fault you're still supposed to blame the carrier as it's their problem. The only time you'd lay the blame on the plane maker directly is the short window (in a perfect world) where an issue is found but they have yet to notify the carriers that run that specific model.
Though there's also the fact that dell may not have the rights to release it, as who knows what the ownership situtation is with it.
A similar example would be if planes had some small piece of classified tech so that it cant be fixed by their guys, they'd have to mail it in and get a new one or something.
Keep in mind both examples are of course gross oversimplifications, there's always gonna be exceptions and whatnot.
The majority of the sources for each individial component is available in one form or another due to other devices using the same parts, but having the source and being able to glue them together into something worth using are two entirely seperate worlds. The gap to bridge is still pretty damn big. (also keep in mind drivers still have to be updated for ICS, gb source level drivers still arnt enough by themselves unless they're coincidentially unchanged from GB -> ICS)
Bump for some ics
I working since a few weeks on an ics rom, but I can't say how long it will take because I don't have much time to make further
I'm down, I'm holding off on getting the Note for two reasons... 1. Of the wack a** posts and newbies w/ the note that just refuse to believe the device has a flaw... The "Shipping" Thread/ Post had to be one of the g**** post I ever witnessed lol!... Plus the folks that swear its worth $300 bucks but cried a river to ATT/BB when it dropped to $150 within a day but then say they would pay $300 for it again : /
2. The Streak has served me well for the past 2yrs...I'm loyal to things that are loyal to me.
I want ICS on this Device big time... If not, further dev on CM7 and/or CM9.. If someone can make it happen, I will make that individual a happy person..pz
I'd happily donate $20+ for ICS or CM9!
Thanks to all the developers out there that have kept the streak alive!
bauner said:
I working since a few weeks on an ics rom, but I can't say how long it will take because I don't have much time to make further
Click to expand...
Click to collapse
Any updates to your status? I'm holding off for dear life for a upgrade/update for CM7/CM9 or ICS..If not then it's fine and I greatly appreciate everyone's efforts, this just may be the last night I use my beloved streak as a full time phone... almost 2yrs, same device the entire time..
I'm bumping this thread because it looks like DJSteve may be up for the task. http://forum.xda-developers.com/showthread.php?t=1992263&page=2
Just a quick note of thanks to OaT for his superior builds and the sadness he's now discontinued them .
I was first in line of the hungry hoards who insatiably devoured every mouthwatering release - from LnT_Beats to Linaro experimental builds, and to my shame never got a word of thanks or feedback out to the master chef! Unfortunately this pattern of general behaviour I believe contributed to the demise of this coveted build.
I tried a number of times to feedback on OaT's threads but was blocked by forum rules (hadn't hit the 10 x post threshold) and frustrated by this it was easy not to make the effort and feedback on this fine ROM. Apologies for this!
Nevertheless, OaT releases won't be forgotten, and my sincere thanks for his superb efforts on a thoroughly enjoyable and expert release.
Cheers,
P
I'm going to get eaten alive for saying this, but I think the whole quitting due to not receiving thanks was a bit childish... He knew people liked his ROM, mostly by the number of people he knew downloaded his ROM... If he wanted to quit for personal reasons then whatever, that's all good, it's his life. Just, I don't really get the importance of a thank you button on a message board.
Sent from my Galaxy Nexus using xda app-developers app
Certain people just get a rush out of being able to show other devs how many "thanks" they have. It's the same as like-whores on facebook.
He wanted feedback on the ROM as well, not just thanks.
bananagranola said:
He wanted feedback on the ROM as well, not just thanks.
Click to expand...
Click to collapse
What bananagranola just said is the biggest reason the man pulled the ROM.... Just as most users here are too lazy to search before asking questions... they're too lazy to fulfill the development request for feedback so he can make the ROM that THEY like using better... and those same people whining about the links being pulled are the same ones that conveniently forget to remember that's why he pulled links... not for the THANKS but for THEIR lack of ability to provide a simple request
For anyone with several devices can see... this is happening all over xda... the devs are tiring of the leeches that download and then simply whine and complain when things aren't all roses with their devices
Sent from my AOKP M6 TouchPad using TapaTalk 2
cdzo72 said:
What bananagranola just said is the biggest reason the man pulled the ROM.... Just as most users here are too lazy to search before asking questions... they're too lazy to fulfill the development request for feedback so he can make the ROM that THEY like using better... and those same people whining about the links being pulled are the same ones that conveniently forget to remember that's why he pulled links... not for the THANKS but for THEIR lack of ability to provide a simple request
For anyone with several devices can see... this is happening all over xda... the devs are tiring of the leeches that download and then simply whine and complain when things aren't all roses with their devices
Sent from my AOKP M6 TouchPad using TapaTalk 2
Click to expand...
Click to collapse
I said my thanks, and never complained. I didn't provide much feedback, because to me, it just felt like complaining and I knew I didn't have that right. Oh well, water under the bridge now... RIP touchpad for now. These days remind me of when bumblebee stopped supporting lg v500. Development died for months and I ended up selling the thing due to it.
Sent from my aokp_tenderloin using xda app-developers app
If this thread turns into a big arguing pit, I'll close this too. Please keep your posts civil and don't start arguments.
Noellenchris
Is the TP on its last Android leg?
It doesn't bear discussion as to the "why" OaT took down the ROM. It was a personal decision made by an individual for whatever rationale he/she determined was in their best interest to have a happy life. I have to respect that if I want others to respect my discussion and decisions as well. Many thanks for the time and effort that OaT put forward, but I'm not sure where to go from here.
The TouchPad isn't going to move forward. It's a static technology that HP as a manufacturer isn't going to come back to. At least not in its current incarnation. HP is coming back to the tablet world - just not at this moment, and not with WebOS. If you read the news, HP will be back in this space with Win 8 and tablets in the future.
Tech doesn't stand still, and as people's interests change on a non-standard / open sourced product - it's lifecycle is only determined by the people able to move it forward, and the demand people are placing on a limited supply item.
Reading the writing on the walls, the HP TouchPad is reaching the end of its (Android) life - for better or worse. Now it's up to those of us who own the TouchPad to determine just how long to hang onto it before moving on. Do you settle on a latest release of CM9, or hope that someone pushes CM10 forward and gets audio, HD video and all the other bells and whistles to the point of CM9? (Let's just all assume the camera is the great white whale for devs.)
It's only after the death of an artist that the world mourns their contributions. With OaT dropping out - I don't know where to put my focus. I don't know which devs are still around working diligently on CM10 versus the crew working on CM9.
--McBean
bananagranola said:
He wanted feedback on the ROM as well, not just thanks.
Click to expand...
Click to collapse
cdzo72 said:
What bananagranola just said is the biggest reason the man pulled the ROM.... Just as most users here are too lazy to search before asking questions... they're too lazy to fulfill the development request for feedback so he can make the ROM that THEY like using better... and those same people whining about the links being pulled are the same ones that conveniently forget to remember that's why he pulled links... not for the THANKS but for THEIR lack of ability to provide a simple request
For anyone with several devices can see... this is happening all over xda... the devs are tiring of the leeches that download and then simply whine and complain when things aren't all roses with their devices
Sent from my AOKP M6 TouchPad using TapaTalk 2
Click to expand...
Click to collapse
I'll try to make it official and clear here. The primary reason for me discontinuing development and pulling the links was the lack of feedback on the new Beats Audio in the new LnTBA. I don't have the hifi sound equipment to test that, and with 60 year old ears that are only able to hear middle range sounds, I'm not sure even if I did I would be able to tell if the new BA was an improvement or not.
The lack of feedback when specifically asked for, even initially when I asked for testers when I began to consider publishing the ROM, has been a real disappointment. In fact I initially expanded my testers list from ~20 to ~40 because of people asking me to 'please' let them test and 'promising' feedback. In the end I got at most a handful of thoughtful responses.
So in this last round where I requested feedback on LnTBA, I set the bar pretty low the day I posted it; I told myself if I only got 1 response when the download count reached 100 or more that would be enough, understanding that not everyone flashes as soon as they download. Ultimately there were ~250 downloads of LnTBA within ~24 hours of it being posted. Still, there was not one response, "none, zero, nada"!
In regards to the lack of folks hitting the "thanks" button, it should be obvious that if that were the real reason to discontinue development I would have stopped publishing the ROMs long ago.
Let me end on a somewhat positive note saying I do not know if or when I will restart publishing, after all the thread says "discontinued" and not for example "abandoned" in the CM sense. But rest assured development on my end for TPad is certainly still continuing. In fact I had the first bit of progress on sound for JB last night/today.
O.a.T. said:
Let me end on a somewhat positive note saying I do not know if or when I will restart publishing, after all the thread says "discontinued" and not for example "abandoned" in the CM sense. But rest assured development on my end for TPad is certainly still continuing. In fact I had the first bit of progress on sound for JB last night/today.
Click to expand...
Click to collapse
OaT, that's awesome!
I do respect your decision to pull your ROMs due to lack of feedback. It goes back to something I say almost every day... If I don't know there's a problem, I can't fix it. I'm trying to get my 10 posts in so, hopefully, when/if you do make another release, I am able to provide input in the dev forum.
O.a.T. said:
I'll try to make it official and clear here. The primary reason for me discontinuing development and pulling the links was the lack of feedback on the new Beats Audio in the new LnTBA. I don't have the hifi sound equipment to test that, and with 60 year old ears that are only able to hear middle range sounds, I'm not sure even if I did I would be able to tell if the new BA was an improvement or not.
The lack of feedback when specifically asked for, even initially when I asked for testers when I began to consider publishing the ROM, has been a real disappointment. In fact I initially expanded my testers list from ~20 to ~40 because of people asking me to 'please' let them test and 'promising' feedback. In the end I got at most a handful of thoughtful responses.
So in this last round where I requested feedback on LnTBA, I set the bar pretty low the day I posted it; I told myself if I only got 1 response when the download count reached 100 or more that would be enough, understanding that not everyone flashes as soon as they download. Ultimately there were ~250 downloads of LnTBA within ~24 hours of it being posted. Still, there was not one response, "none, zero, nada"!
In regards to the lack of folks hitting the "thanks" button, it should be obvious that if that were the real reason to discontinue development I would have stopped publishing the ROMs long ago.
Let me end on a somewhat positive note saying I do not know if or when I will restart publishing, after all the thread says "discontinued" and not for example "abandoned" in the CM sense. But rest assured development on my end for TPad is certainly still continuing. In fact I had the first bit of progress on sound for JB last night/today.
Click to expand...
Click to collapse
This is unbelievably great news. Many people like your Roms and have great experiances with them. As you said I don't flash right away. i dont have alot of time to play with my touchpad so when I get around to it, all the issues that I have seen are usually already posted. Plus I'm not a heavy user of so I dont see many of the issues.
As far as Beats Audio, I've only flashed it on my LG revolution and it made it worse. Otherwise if a Rom has it in it for the touchpad I haven't noticed. I also don't use audio that much. I'm basically explaining that I do like your ROMs but i think my feedback might not make an impact.
OaT the TP God
O.a.T. said:
I'll try to make it official and clear here. The primary reason for me discontinuing development and pulling the links was the lack of feedback on the new Beats Audio in the new LnTBA. I don't have the hifi sound equipment to test that, and with 60 year old ears that are only able to hear middle range sounds, I'm not sure even if I did I would be able to tell if the new BA was an improvement or not.
The lack of feedback when specifically asked for, even initially when I asked for testers when I began to consider publishing the ROM, has been a real disappointment. In fact I initially expanded my testers list from ~20 to ~40 because of people asking me to 'please' let them test and 'promising' feedback. In the end I got at most a handful of thoughtful responses.
So in this last round where I requested feedback on LnTBA, I set the bar pretty low the day I posted it; I told myself if I only got 1 response when the download count reached 100 or more that would be enough, understanding that not everyone flashes as soon as they download. Ultimately there were ~250 downloads of LnTBA within ~24 hours of it being posted. Still, there was not one response, "none, zero, nada"!
In regards to the lack of folks hitting the "thanks" button, it should be obvious that if that were the real reason to discontinue development I would have stopped publishing the ROMs long ago.
Let me end on a somewhat positive note saying I do not know if or when I will restart publishing, after all the thread says "discontinued" and not for example "abandoned" in the CM sense. But rest assured development on my end for TPad is certainly still continuing. In fact I had the first bit of progress on sound for JB last night/today.
Click to expand...
Click to collapse
OaT,
I was out of town during that release (in Alaska, no internet), and I don't use BA at all, ever. I think it's a gimmick. I will say that your 829 build is amazing, and probably the best OS I have used on any tablet ever.
I don't agree with your decision to pull all your roms. It IS your decision, but I know hundreds of TP users out there (most probably lurkers that don't even post on XDA) have benefited from your superior roms, and it seems like helping people in the future (or even just currently) would be the "right" thing to do.
Thank you for:
A) Your roms
B) The explanation of your sudden disappearance
C) Giving us some hope for the future
D) Continuing your development
I can understand your frustrations about testers. Doing a bunch of work and not getting feedback can be a real drag. I'll try to be more vocal in the future. Hell, I'll start right now.
The 829 build is GREAT. The battery lasts forever. I have been getting occasional FCs here and there, in particular the holo launcher is DOA on this build. Apex works great (as usual), I don't really like GO launcher. I think it's kind of a mess. This is my daily driver now because the battery is so much better than the 819 JB build. Google Now voice input doesn't work at all for me (using OaT gapps 429). The rest of Google Now works great.
Feel free to let me know if you need more testing with something specific, but don't expect it too quickly. I'm married, new baby, play in a band, and have a full time IT job. I will get to it late at night on Thursdays or Sunday afternoon though, if I can.
Rhy
I for one am guilty as charged in the "no feedback" issue, my bad. I've used and enjoyed your roms and most definitely should have participated in helping squash the bugs. Sorry buddy. On another note though, the stupid rom is just so damn solid I really had nothing to say I would kinda feel like a whiner if I mentioned the occasional fc. I am still amazed that this old webos tablet can even run android, let alone run it well.
Sent from my cm_tenderloin using Tapatalk 2
ItsDon said:
I for one am guilty as charged in the "no feedback" issue, my bad. I've used and enjoyed your roms and most definitely should have participated in helping squash the bugs. Sorry buddy. On another note though, the stupid rom is just so damn solid I really had nothing to say I would kinda feel like a whiner if I mentioned the occasional fc. I am still amazed that this old webos tablet can even run android, let alone run it well.
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Have to echo ItsDon. I don't feedback much either because the thing works so damn well. Thanks again OaT.
OaT, your ROM is the best.
Sent from my cm_tenderloin using Tapatalk 2
As for me, I am a newb for xda, not a lurker, and couldn't post feedback on the dev section til I got the requirements done. Something like that.
Sent from my YP-G70 using xda app-developers app
hanjosep said:
As for me, I am a newb for xda, not a lurker, and couldn't post feedback on the dev section til I got the requirements done. Something like that.
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
I. for one, could not leave feedback because I didn't have enough posts. They should remove this requirement from the forum because I think many people can't leave feedback because of this requirement. Some people (including myself) don't like posting random comments to increase their posts and want to get to the point.
Regardless, thanks for everything you've done so far OaT.
Sad to see that on a weekend when I don't check up on OAT thread I miss out on an update. As far as beats feedback goes off the top of my head I ran with the beats build of 7/06 and 7/29. Before that I ran the standard version of 6/03. On a whim I switched over to the non beats version of 7/29 and never looked back. I believe I stuck to the standard version of 7/29 because overall audio clarity seemed to be better on the standard. Easiest way for me to say that is at equal volume the standard seemed louder? Again this was from memory, the testing was conducting in the best setting, and I wasn't trying that hard. In all honesty I think what I was trying to see if there would be a significant difference between the two and if there was I would keep my preferred version. Since I'm running the 7/29 non beats still I assume I found no significant difference. I would like to add that I found no difference even in webos with beats on or off.
This is too little too late, but this has been my personal experience. I used Audio Technica CKS77 iems. Thank you for all you have done OAT, your light n tasty philosophy was something I really appreciated when I was looking at roms and was what made pick your rom first. I never bothered to try the rest
Legion021 said:
I. for one, could not leave feedback because I didn't have enough posts. They should remove this requirement from the forum because I think many people can't leave feedback because of this requirement. Some people (including myself) don't like posting random comments to increase their posts and want to get to the point.
Regardless, thanks for everything you've done so far OaT.
Click to expand...
Click to collapse
I second that. And the "thanks" button does not show until you make your first post. I went crazy trying to find it.
It's just sad that I never cared for oat's roms until now that he disappeared. I also don't think it's fair that a small portion of people were able to download the latest build and others were not. In case someone has the latest build and it didn't break any rules and disrespect the developer then please share.
Sent from my GT-I9300 using Tapatalk 2
This [New Approach to get HTC to listen.] thread was OP by hasoon2000, and stickied into Tony Stark's "General sticky."
It is more important now than ever to ask HTC to lend a hand, especially in making some unreleased code available.
Please see the link for the simple instructions.
Thanks,
pbergonzi
pbergonzi said:
This [New Approach to get HTC to listen.] thread was OP by hasoon2000, and stickied into Tony Stark's "General sticky."
It is more important now than ever to ask HTC to lend a hand, especially in making some unreleased code available.
Please see the link for the simple instructions.
Thanks,
pbergonzi
Click to expand...
Click to collapse
I followed the advice, contacting them, and within 12 hours got this reply, and attempted to provide the requested information:
"Dear (pbergonzi),
Thank you for contacting HTC Technical Support.
(pbergonzi), first of all I would like to thank you for being a member of our family of smart mobile devices. In this case, I want to make sure your request is passed along to our proper department. Remember your thoughts are imperative for us to grow as a community. Our goal is always to provide you with top of the line devices as well as a spectacular HTC experience.
In this case, in order to pass this information to the proper department, I will like to know the following:
• Carrier
• Android version / Software version requesting source code for
• Radio Version Note: This is Baseband version on Android devices
• Serial Number/MEID/ IMEI/ESN
• Software Number
• Full Name
• Email Address
• Contact Number
• Mobile Number
• Preferred Contact Time
• Time Zone
• Carrier
I look forward to your reply with the necessary informaiton. Please do not hesitate to contact us through http://www.htc.com/us/contact/email/ or call us at +1-866-449-8358 from (8 Am – 1 Am) ET, 7 days a week or you can reply to this email by clicking on the link below.
Thank you for being a member of our HTC community and I wish you a good day!
If this answers your comment or question, please click here to complete the process.
To submit another comment, please click here.
Sincerely,
The HTCDev Team
Want to see what others are saying? Have a question to ask other HTCDev fans?
Follow us on Twitter www.twitter.com/htcdev
Explore our development resources www.htcdev.com
We are unable to receive replies to this email account. Please visit us at www.htcdev.com if you have any questions or need further assistance."
I can only imagine what would happen if 5 million more of us contacted them.
pbergonzi said:
I followed the advice, contacting them, and within 12 hours got this reply, and attempted to provide the requested information:
"Dear (pbergonzi),
Thank you for contacting HTC Technical Support.
(pbergonzi), first of all I would like to thank you for being a member of our family of smart mobile devices. In this case, I want to make sure your request is passed along to our proper department. Remember your thoughts are imperative for us to grow as a community. Our goal is always to provide you with top of the line devices as well as a spectacular HTC experience.
In this case, in order to pass this information to the proper department, I will like to know the following:
• Carrier
• Android version / Software version requesting source code for
• Radio Version Note: This is Baseband version on Android devices
• Serial Number/MEID/ IMEI/ESN
• Software Number
• Full Name
• Email Address
• Contact Number
• Mobile Number
• Preferred Contact Time
• Time Zone
• Carrier
I look forward to your reply with the necessary informaiton. Please do not hesitate to contact us through http://www.htc.com/us/contact/email/ or call us at +1-866-449-8358 from (8 Am – 1 Am) ET, 7 days a week or you can reply to this email by clicking on the link below.
Thank you for being a member of our HTC community and I wish you a good day!
If this answers your comment or question, please click here to complete the process.
To submit another comment, please click here.
Sincerely,
The HTCDev Team
Want to see what others are saying? Have a question to ask other HTCDev fans?
Follow us on Twitter www.twitter.com/htcdev
Explore our development resources www.htcdev.com
We are unable to receive replies to this email account. Please visit us at www.htcdev.com if you have any questions or need further assistance."
I can only imagine what would happen if 5 million more of us contacted them.
Click to expand...
Click to collapse
I hate to rain on your parade, but you're referencing a nearly two year old post that was made at a time when HTC wasn't unlocking devices or providing source code for them. Tens of thousands did write letters and signed several online petitions, the most famous of which was at change.org. HTC eventually did bow to pressure and provided the means to unlock boot-loaders and released the source code. It's why we and other HTC owners can run different kernels and ROMs now, without jumping through hoops trying crazy hacks and exploits to do so.
The issues are now with the component manufacturers like Texas Instruments and Qualcomm who have yet to release up to date open sourced drivers for newer kernels. Heck, it took petitions and a letter writing campaign just to get them to release the stale sources we have now that were already nearly two years old. Don't hold your breath that they'll be inclined to release any newer ones for a device as old as ours is.
Sorry to give you the bad news but you're jumping in with this pretty late in the game. Our device wasn't a big seller, and was eclipsed by lighter more powerful units within 3 months of its release. All but a handful of devs left for greener pastures long ago. What we have left is a small group of dedicated diehards who are doing the best they can with what they have to work with. Just be thankful that we have them, and that any work is still being done here.
Look at this forum, on a busy day there's maybe 6-7 posts, but on average 2-3. Were lucky that the powers that run this place haven't relegated us to "legacy" status yet. Again, I don't want to down you out, but even if every active reader of this forum were to run out and immediately do as you suggest, we'd be lucky to get a hundred sent in. I'm sorry, but these are the facts. To believe anything else would be at best hopeless optimism, or at worst pure fantasy. Just my opinion.
Ciao
Oh, thanks Odysseus. The history lesson was edifying and poignant. Since the subject was stickied, it still seemed relevant.
Nevertheless, after ravike mentioned just recently about communicating with someone there, I thought communication at the very least wouldn't hurt, and who knows if someone somewhere might just change something. I think that energy spent in changing my mind would be better spent and more psychically rewarding directed toward HTC, even though presumably useless. You for example, are certainly articulate enough that your words might well work a lasting sympathetic response in a developer, and who knows where that will go, even if he doesn't directly reply in kind--he might for example, be kinder to the person who brings his coffee, just as an example.
Granted, 5 million members of xda are not about to contact HTC, however, as the little sparrow, with feet pointed skyward to prevent it from falling, said to the chuckling farmer who doubted him, "One does what one can."
Sorry to Burst Your Bubble
Odysseus1962 said:
I hate to rain on your parade, but you're referencing a nearly two year old post that was made at a time when HTC wasn't unlocking devices or providing source code for them. Tens of thousands did write letters and signed several online petitions, the most famous of which was at change.org. HTC eventually did bow to pressure and provided the means to unlock boot-loaders and released the source code. It's why we and other HTC owners can run different kernels and ROMs now, without jumping through hoops trying crazy hacks and exploits to do so.
The issues are now with the component manufacturers like Texas Instruments and Qualcomm who have yet to release up to date open sourced drivers for newer kernels. Heck, it took petitions and a letter writing campaign just to get them to release the stale sources we have now that were already nearly two years old. Don't hold your breath that they'll be inclined to release any newer ones for a device as old as ours is.
Sorry to give you the bad news but you're jumping in with this pretty late in the game. Our device wasn't a big seller, and was eclipsed by lighter more powerful units within 3 months of its release. All but a handful of devs left for greener pastures long ago. What we have left is a small group of dedicated diehards who are doing the best they can with what they have to work with. Just be thankful that we have them, and that any work is still being done here.
Look at this forum, on a busy day there's maybe 6-7 posts, but on average 2-3. Were lucky that the powers that run this place haven't relegated us to "legacy" status yet. Again, I don't want to down you out, but even if every active reader of this forum were to run out and immediately do as you suggest, we'd be lucky to get a hundred sent in. I'm sorry, but these are the facts. To believe anything else would be at best hopeless optimism, or at worst pure fantasy. Just my opinion.
Ciao
Click to expand...
Click to collapse
+1
@pbergonzi I do appreciate that you are trying to help, but the Amaze is LONG dead. If you decide to visit HTC's official website, the Amaze has vanished. They are pretending it never existed. The only things left are old drivers and antiquated software support from HTC (doesn't apply to us anymore). From what I saw, they only released source because they would have been breaking the GPL, thus decreasing their reputation as a smartphone manufacturer.
Also, it's not that HTC doesn't want to support us, it's that they can't. Texas Instruments doesn't support our chipset, and never will because this phone didn't sell. HTC has absolutely no obligation to release source code for less than a dozen hobbyist developers. They have better things to do, like develop for the HTC One. Why would they care about us. That's the ugly unwritten truth about companies.
If they do decide to spontaneously resume support, I will buy 3 goats, paint numbers "1", "2", and "4" on them and release the goats while in school and let them run wild!
pbergonzi said:
Oh, thanks Odysseus. The history lesson was edifying and poignant. Since the subject was stickied, it still seemed relevant.
Nevertheless, after ravike mentioned just recently about communicating with someone there, I thought communication at the very least wouldn't hurt, and who knows if someone somewhere might just change something. I think that energy spent in changing my mind would be better spent and more psychically rewarding directed toward HTC, even though presumably useless. You for example, are certainly articulate enough that your words might well work a lasting sympathetic response in a developer, and who knows where that will go, even if he doesn't directly reply in kind--he might for example, be kinder to the person who brings his coffee, just as an example.
Granted, 5 million members of xda are not about to contact HTC, however, as the little sparrow, with feet pointed skyward to prevent it from falling, said to the chuckling farmer who doubted him, "One does what one can."
Click to expand...
Click to collapse
Listen, I hope my comments haven't dampened your enthusiasm. I truly love this device. It's the perfect size for my needs, takes great photos, and connects to the net much faster than the HD2 it replaced. The hardware still holds its own 3 years after release. It was the top of the line when it came out and the build quality that one would expect from a high-end product is evident wherever you look on the device.
The only problem with it is software, in particular an outdated OS. The very software that allows lesser devices to perform better than this, is what's holding it back. Please don't be discouraged, instead learn what you can so that you too can contribute to our small, but loyal community. Together, each in his own way, we can continue to keep the amaze alive.
Maybe it should be "New Approach to get Texas Instuments to listen."
Like for example, in the TI Engineer to Engineer community, where ravike14 is trying to get a little satisfaction regarding unreleased code:
http://e2e.ti.com/support/low_power_rf/f/307/p/305896/1089531.aspx#1089531
Hello everyone!
I didn't know where to really put this and the forums are still one of the places I feel most comfortable on the web.
In 2019 we did a far better job of covering more new PC hardware components than the previous year. Some of our reviews took longer than expected, but I stand behind my findings. Late in the year some personal matters required that I put the brakes on releasing new reviews. We ended the year with more reviews than before, but we still start 2020 with several reviews in the pipeline that were not completed last year.
In the past year we've taken your feedback. We understand not everyone is happy when a review doesn't come out the same day as the product releases. For those outlets this is their primary coverage. We work with what we can, and I'm very thankful that XDA continues to support the coverage as something beyond its primary coverage of Android and Android devices.. I do believe that our tests and reviews are both useful and necessary, no matter when they go live. Our continued focus on Linux serves an audience that even now still has very few in-depth reviews globally. Investigating situations that may be missed not only provides answers for questions that may be unanswered, but as I found out recently those lessons can still give answers years later.
I'm also very thankful for the XDA leadership and Portal team in their support and flexibility to continue this coverage while I am still dealing with some very serious personal matters. I wish at some point that I could explain just what is going on and how debilitating that can be at times. I suspect those who have gone through similar situations would understand. The only thing I can say is to please always take care of those around you. This goes beyond friends and family - think of the people you work or go to school with. How about the person you run into every morning? Everyone has their own life and not everyone may be having an easy go at it. Sometimes the hardest thing for us is to reach out for help. For others, that hardest thing may be offering help to others.
Try to help others when you can. When you need help, ask. You may find support in places you never expected. If you think something is going on that they may not be able to talk about, at least reach out and see if they may need help. Offer to be an ear or to even listen. They may not be able to tell you what's going on. They may not be able to take that assistance. But sometimes just knowing that there is support may do more than you see at the time. Donate not just to the big causes, think about how you can help others in your community. We're all trying to make our way through that journey that we call life.
I expect to resume writing again soon. Reviews where the tests have already been completed will be first up. Then we'll start with the reviews of components already here and ready to go into the test bench. I'm also looking into the possibility of resuming videos - something I stopped when I relocated in 2018. Most of the "behind the scenes" changes required for me to resume that was addressed last year. My biggest concern is honestly creating enough of a finished space so I don't have to set up and tear down between videos.
We've got even more planned for 2020 than we did the year before, so hope you'll stick around and continue reading our foray into something more than Android on XDA!
I'll review any hardware you ship to me!!!
I'll write a meticulous professional article informed by 30 years of reading hardware websites / BBSes.