Figure we can keep the back and forth here and out of the R&D thread...
Sent from my SCH-I535 using xda premium
I'm curious how closely the USCellular model is to Verizon's and if it is the USCellular model that Samsung will sell as a "developers edition"
Any ideas?
I hope it's not too late. That thread seems long gone... I'm just glad people are staying out of AdamOutler's r&d thread. They actually seem to be getting somewhere.
Wontfinishlast said:
I hope it's not too late. That thread seems long gone... I'm just glad people are staying out of AdamOutler's r&d thread. They actually seem to be getting somewhere.
Click to expand...
Click to collapse
There's some very intelligent people working in there. It amazes me.
Thanks for creating this thread. I keep an eye on the bootloader threads and get tired of having to suffer through pages and pages of people *****ing and moaning about everything related to the bootloader issue except the actual progress in development.
Sent from my LOCKED (Verizon, you suck), SCH-I535.
For anyone interested, I submitted a complaint to the FCC regarding the locked bootloader on the GS3. If you'd like to do the same, go to fcc.gov and click on file a complaint. Then choose wireless provider and then choose the option related to deceptive actions. There is a 1000 character limit to your complaint. Here is the text of my complaint.
Verizon is the only major carrier to have released the Samsung Galaxy SIII with a locked bootloader. There was nothing in Verizon's advertised specs about a locked bootloader. Their explanation is that the device is locked to maintain the security and integrity of the network. However, they are currently selling another Samsung phone, the Galaxy Nexus which has an unlockable bootloader. Also, Verizon has announced a "developer edition" of the Galaxy SIII with an unlockable bootloader for use on Verizon's network. That device must be purchased directly from Samsung for $599. How can Verizon claim a network security and integrity issue and then sell, offer and allow such devices on their network? I feel that Verizon has tricked many customers into paying for a device that they can't use to it's full potential. They know that "security" is a great loophole for complying with the letter of their Auction 73 Block C requirements while totally violating the spirit of that agreement.
That complaint is 990 characters. If you'd like to copy it for your own use, please feel free to do so. Hopefully, enough of us will do this to get the attention of the FCC, consumer organizations and those in positions of influence over the wireless industry.
Sent from my LOCKED (Verizon, you suck), SCH-I535.
I didn't get a chance to file a complaint with the FCC last night but will tonight.
Sent from my SCH-I535 using xda premium
Filed mine yesterday..
Got a call from VZW customer service today. They asked if I was content with my recent upgrade!
She agreed with me that often people buy Androids instead of iPhones because Androids are so customizeable. I expected to be able to use an OS of my choosing on this phone, so I am upset that Verizon locked the bootloader. She understood and sympathized, and now on a server somewhere in the world, there's a short note stating that I'm unhappy with my upgrade.
makogaleos said:
Got a call from VZW customer service today. They asked if I was content with my recent upgrade!
She agreed with me that often people buy Androids instead of iPhones because Androids are so customizeable. I expected to be able to use an OS of my choosing on this phone, so I am upset that Verizon locked the bootloader. She understood and sympathized, and now on a server somewhere in the world, there's a short note stating that I'm unhappy with my upgrade.
Click to expand...
Click to collapse
Hahaha.. awesome!
I understand the notes on my Verizon account are "colorful."
This is Julius Genachowski , head of the FCC.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does this look like a person who knows what a locked vs. unlocked bootloader is? You guys are shooting over the heads of your audience by assuming they know the terms you're using.
BarryH_GEG said:
This is Julius Genachowski , head of the FCC.
Does this look like a person who knows what a locked vs. unlocked bootloader is? You guys are shooting over the heads of your audience by assuming they know the terms you're using.
Click to expand...
Click to collapse
Help us draft a response to help describe the issues, without losing our audience then.
ancashion said:
Help us draft a response to help describe the issues, without losing our audience then.
Click to expand...
Click to collapse
Now now. I assume Gary H has waaaaay better things to do than constructively help a minority of peers, like post rude and useless commentary in Internet forum threads created to provoke attention to a problem that shouldn't exist in the first place.
Sent from my SCH-I535 using xda premium
Honestly, with the latest kexec method, I'm not sweating the boatloader anymore
Sent from my SCH-I535 using xda app-developers app
wera750 said:
Honestly, with the latest kexec method, I'm not sweating the boatloader anymore
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Now I may be wrong here because I've never flashed a rom but come to the S3 from an X2 so I've done my time with encrypted boot-loaders, but-
I thought we could change settings/features/etc. on each Rom, but, changing the base kernel of the OS is impossible. Thus, when a new OS is released from Google- say key lime pie, and it drastically changes the kernel, we will forever be prevented from putting that on our device.
Again, I may be wrong. My understanding of it is very limited.
---------- Post added at 09:13 AM ---------- Previous post was at 09:12 AM ----------
jaj6503 said:
Now now. I assume Gary H has waaaaay better things to do than constructively help a minority of peers, like post rude and useless commentary in Internet forum threads created to provoke attention to a problem that shouldn't exist in the first place.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Damn- I'm already out of thanks to give.
I'd give you a gold star, but there ain't any. how about a :good:
jaj6503 said:
Now now. I assume Gary H has waaaaay better things to do than constructively help a minority of peers, like post rude and useless commentary in Internet forum threads created to provoke attention to a problem that shouldn't exist in the first place.
Click to expand...
Click to collapse
It's "Barry" and I have no problem helping you guys.
"People choose Android phones for their openness. That openness allows portability so we can use the phones we've purchased from a single carrier on other carriers so that, based on the free market competition the FCC fosters, we have choices. Up until Verizon launched the new Samsung Galaxy SIII which is projected to sell in the tens of millions, Verizon (like all the other carriers) supported Android's openness and portability. With this new device, Verizon has locked the bootloader (the ability for users to modify the phone) limiting its portability. They did so without any communication with customers only finding out after entering in to a 2-year binding agreement with penalties. If other carriers follow Verizon’s dangerous precedent, and it’s reasonable to think they will, it runs contra to everything the FCC works so diligently to uphold. ”
BarryH_GEG said:
It's "Barry" and I have no problem helping you guys.
"People choose Android phones for their openness. That openness allows portability so we can use the phones we've purchased from a single carrier on other carriers so that, based on the free market competition the FCC fosters, we have choices. Up until Verizon launched the new Samsung Galaxy SIII which is projected to sell in the tens of millions, Verizon (like all the other carriers) supported Android's openness and portability. With this new device, Verizon has locked the bootloader (the ability for users to modify the phone) limiting its portability. They did so without any communication with customers only finding out after entering in to a 2-year binding agreement with penalties. If other carriers follow Verizon’s dangerous precedent, and it’s reasonable to think they will, it runs contra to everything the FCC works so diligently to uphold. ”
Click to expand...
Click to collapse
Thanks for your post, Barry.
FCC is not ignorant to their own laws. That is, their jobs, after all. It is okay to include a bit of legalese in this case. Maybe mentioning Block C requirements §27.16(e).
I think you guys are barking up the wrong tree though with the encryption of the bootloader locking down the OS. That, they don't care about which has already been proved by Verizon's response to the Razr FCC complaint suggesting it was for "customer service requirements" and "Network security."
Section (e) of §27.16 also includes a blip about the locking down of the device to prevent said device from being used on a different network.
Verizon, will have to explain the reasonableness of keeping an encrypted lock on your device after you've decided to make the switch.
But, for it to work, you must first be truthfully denied by Verizon for this request. Only then, can you back them into a corner.
Truthfully, this will work for all 4g devices, from the Razr to the S3 with encrypted bootloaders.
I explain in more detail here, however, I got very few responses as it think it was over the heads of most.
Really, it's quite simple and again, VZW will have to explain how the action is reasonable, which I can't think of one way they can do. Not when I've decided to take this device to a different network. Basically, they'll tell the FCC it's "reasonable" to lock me to VZW's network which is expressly prohibited by that law. I just can't see how they can do it.
Edit- I'm all out of thanks to give so :good:
ancashion said:
Now I may be wrong here because I've never flashed a rom but come to the S3 from an X2 so I've done my time with encrypted boot-loaders, but-
I thought we could change settings/features/etc. on each Rom, but, changing the base kernel of the OS is impossible. Thus, when a new OS is released from Google- say key lime pie, and it drastically changes the kernel, we will forever be prevented from putting that on our device.
Again, I may be wrong. My understanding of it is very limited.
Click to expand...
Click to collapse
I believe you are mistaken.
I came from a Droid 2 Global, where we had a similar situation. We were stuck on the Gingerbread kernel, and with no kexec, we were unable to chain-load a new kernel. We eventually got ICS ports like CM9, but that's because developers made lots of wrappers to make the existing Android ICS framework compatible with the Gingerbread kernel.
This is different from the Galaxy S3, however. We have a working kexec port that allows us to chain-load any custom kernel we want. This means that the bootloader initially loads the original, signed Samsung kernel, and then while that kernel is running, it actually loads our new, unsigned kernel directly on top of the currently running kernel. The unsigned kernel is then the one handling everything. There is pretty much nothing from the kernel-upwards that we can't modify- it's only the lower level stuff, which is pretty much just the bootloader itself.
We now have an auto-kexec method that streamlines the entire process, too. Previously, the kexec/kernel package had to be flashed in recovery before starting Android, otherwise the new kernel would not be loaded. The auto-kexec method keeps everything on a cache partition, and automatically flashes the package with each reboot. Basically the only drawback to our auto-kexec method is that it takes a bit longer to reboot/start the device, because it must first automatically boot into recovery and flash the package.
Still, this method pretty much entirely circumvents the bootloader. Plus, if you've taken a look at the CM9 install guide for our device, the actual installations of ROMs with auto-exec are now as simple as flashing the custom recovery to the device and then flashing a ROM via recovery. It's near-identical to how you normally flash ROMs.
Because of all this hard work, AOSP ROMs with custom kernels are a reality, and I can only hope we'll see official support from the CyanogenMod team and other major ROM teams.
ExodusC said:
I believe you are mistaken.
I came from a Droid 2 Global, where we had a similar situation. We were stuck on the Gingerbread kernel, and with no kexec, we were unable to chain-load a new kernel. We eventually got ICS ports like CM9, but that's because developers made lots of wrappers to make the existing Android ICS framework compatible with the Gingerbread kernel.
This is different from the Galaxy S3, however. We have a working kexec port that allows us to chain-load any custom kernel we want. This means that the bootloader initially loads the original, signed Samsung kernel, and then while that kernel is running, it actually loads our new, unsigned kernel directly on top of the currently running kernel. The unsigned kernel is then the one handling everything. There is pretty much nothing from the kernel-upwards that we can't modify- it's only the lower level stuff, which is pretty much just the bootloader itself.
We now have an auto-kexec method that streamlines the entire process, too. Previously, the kexec/kernel package had to be flashed in recovery before starting Android, otherwise the new kernel would not be loaded. The auto-kexec method keeps everything on a cache partition, and automatically flashes the package with each reboot. Basically the only drawback to our auto-kexec method is that it takes a bit longer to reboot/start the device, because it must first automatically boot into recovery and flash the package.
Still, this method pretty much entirely circumvents the bootloader. Plus, if you've taken a look at the CM9 install guide for our device, the actual installations of ROMs with auto-exec are now as simple as flashing the custom recovery to the device and then flashing a ROM via recovery. It's near-identical to how you normally flash ROMs.
Because of all this hard work, AOSP ROMs with custom kernels are a reality, and I can only hope we'll see official support from the CyanogenMod team and other major ROM teams.
Click to expand...
Click to collapse
Thank you for your reply. I have no more thanks to give so :good: will have to do. I'll try and come back to give the props you deserve.
My apologies for being so thick on it. I've got a ton to learn.
BarryH_GEG said:
This is Julius Genachowski , head of the FCC.
Does this look like a person who knows what a locked vs. unlocked bootloader is? You guys are shooting over the heads of your audience by assuming they know the terms you're using.
Click to expand...
Click to collapse
No but he looks like the type that would have 3 hot female geek interns that could explain it to him. FCC takes the time to figure out the whole situation I dunno how you can judge what someone looks like as to what power they may have... Hes got the finger that could potentially hit the red button. I mean common hes go a red tie! I'll try and file a complaint this weekend. I'm not really cool with the whole 14 day return deal. I want the phone that was advertised because I had to upgrade due the the fact i was forced to... keep in mind they didn't let us know via Verizon to customer communication only through thrid party...
Related
We need to start an "S3 Unlock " campaign on Verizon's and Samsung's facebook and email to make our dissatisfaction more visible. Will this have any impact, I don't know, but it's something easily done with almost no effort that the general consumer and non-development community will easily see.
This has worked in the past with the HTC EVO 3D. If the community can get HTC, a million dollar company to notice, maybe it will work with a billion dollar company.
Why should we send to Samsung when it's Verizon that locked the bootloader? The reason for it is more then likely Verizon will try to pawn it off on Samsung; by saying they locked it or they have to build the unlock tool. So, before this becomes a “blame game” We don't care who is responsible, we just want “Developmental Equality” for all S3's
So as Bob Marley said: “Get up, stand up: stand up for your rights!” and take 3 minutes out of your day to help out the community.
What needs to be done:
Post "S3 Unlock or WE Walk" on Verizon's and Samsung's facebook. This would have a greater impact if it were posted everyday! “Don't let them forget about us!”
Email:
Under subject put: “S3 Unlock Bootloader” and in the body put “S3 Unlock ”
Samsung Contact:
https://www.facebook.com/SamsungUSA
Y.K. Kim
president and Chief Executive Officer of Samsung Electronics America
[email protected]
Dale Sohn
President at Samsung Telecommunications America
[email protected]
https://contactus.samsung.com/custo...estionGeneral.jsp?SITE_ID=591&PROD_ID=G303850
Verizon Contact:
https://www.facebook.com/verizon
Daniel S. Mead
President and CEO
[email protected]
Marni Walden
Executive Vice President and Chief Operating Officer
[email protected]
I understand what you want to do but alot of this is already being done by alot if angry customers. Verizon doesnt seem to care. All they did was blame Samsung.
Doesn't it make more sense that hitting them with a mass amount of posts and emails would do more than maybe 20 emails a day. It would get more attention if even just 1% of Verizon's customers were to flood them with posts and emails..this would be in the numbers up to 250,000 emails and facebook posts. They could still ignore it, but this would create more negative publicity. This is also why I am asking everyone to flood Samsung as well, eventually hopefully one of them will correct the issue. In time and numbers they will get tired of it and deal with us. Have you sent an email to Verizon or posted on their facebook?
Verizon might not admit that they are wrong, but any company is highly concerned about their public image. Facebook and Twitter can be a valuable tool to fight corporate arrogance.
One more thing to do... everyone should write a review on Verizon's web site slamming the locked bootloader, with a suggestion that this is a great phone on any provider but Verizon. I just clicked on the "Read reviews" link for the 32GB blue S3, and 4 out of the first ten reviews mentioned the locked bootloader.
We might never get them to unlock this particular bootloader, but at a minimum it would make them think twice about the future of locked bootloaders.
Verizon is betting on our apathy, so I applaud anyone who is willing to spend a bit of time keeping the heat on Verizon.
If you're serious about trying to piss them off, create an Anti Samsung Facebook page and / or Twitter Account basically blasting them for ****ty things they do, such as slow updates to products, locked bootloader, etc.
I once complained on Twitter about my GT 10.1 and didn't even direct it to them and I had their twitter person contact me and ask me if there was something they could do to help me.
They don't like knowing people are badmouthing them on social networks.
As for Verizon, they're used to people talking smack on them and don't seem the slightest bit phased.
If you're not part of the solution...you're part of the problem
I mean I guess anything's worth a try...but I don't think Verizon cares.
topmetsfan said:
I mean I guess anything's worth a try...but I don't think Verizon cares.
Click to expand...
Click to collapse
They seem to hate me. Emailed the CEO about the bootloader, got the standard letter in the mail about "network security" from some high chair rep. His problem is he said "feel free to call with questions" in the letter, as well as his number. I have called him 5 times in the past 2 weeks, always leaving a message. I have still yet to get a call back. I wont stop til I can voice my opinion and get some answers.
I've been tweeting and posting on their facebook pages that I am unhappy about the locked boot loader and spyware on the phone.
It of course won't do any good, but maybe if other non dev/hacker types see the posts they will inquire or think twice.
dvaderx said:
I've been tweeting and posting on their facebook pages that I am unhappy about the locked boot loader and spyware on the phone.
It of course won't do any good, but maybe if other non dev/hacker types see the posts they will inquire or think twice.
Click to expand...
Click to collapse
But other non dev/hacker types won't understand what a bootloader is and what the difference is between a locked and unlocked.
fluxvalve said:
Verizon might not admit that they are wrong, but any company is highly concerned about their public image. Facebook and Twitter can be a valuable tool to fight corporate arrogance.
One more thing to do... everyone should write a review on Verizon's web site slamming the locked bootloader, with a suggestion that this is a great phone on any provider but Verizon. I just clicked on the "Read reviews" link for the 32GB blue S3, and 4 out of the first ten reviews mentioned the locked bootloader.
We might never get them to unlock this particular bootloader, but at a minimum it would make them think twice about the future of locked bootloaders.
Verizon is betting on our apathy, so I applaud anyone who is willing to spend a bit of time keeping the heat on Verizon.
Click to expand...
Click to collapse
Why they even try to lock them I don't even get. It just seems like a waste of their time and resources. Just look at the s3, it was basically cracked before release and we already can do just about anything we want on it. It makes them look bad and does nothing and it makes even less sense when they have unlocked phones on their network. Bunch of dummies if you ask me
---------- Post added at 08:32 AM ---------- Previous post was at 08:26 AM ----------
ddggttff3 said:
They seem to hate me. Emailed the CEO about the bootloader, got the standard letter in the mail about "network security" from some high chair rep. His problem is he said "feel free to call with questions" in the letter, as well as his number. I have called him 5 times in the past 2 weeks, always leaving a message. I have still yet to get a call back. I wont stop til I can voice my opinion and get some answers.
Click to expand...
Click to collapse
When you do, If you do, point out they sell unlocked phones on their network and that virtually every phone they sell has been hacked and its just a waste of their time.
piiman said:
Why they even try to lock them I don't even get. It just seems like a waste of their time and resources. Just look at the s3, it was basically cracked before release and we already can do just about anything we want on it. It makes them look bad and does nothing and it makes even less sense when they have unlocked phones on their network. Bunch of dummies if you ask me
Click to expand...
Click to collapse
If my x2 bootloader wasn't locked down like it is, ii wouldn't have purchased a new phone. Hardware is staying viable for a longer time than they would like, but, by locking down the software used they can obsolete your device long before the hardware is obsolete. Those who are savvy enough to hack it and put what they want on it also upgrade quick to the newest hardware for the wow factor and vzw knows this. Locking the device down prevents people like me from upgrading software easily, thus forcing a hardware upgrade- to achieve my desire for a software upgrade.
It's quite simple really. Phone sales. If any Joe-Schmoe could upgrade their droidx2 to jellybean, they wouldn't see that phone sale. No phone sale = no new 2 year contract.
They don't market the hardware specs at all like they market the OS.
It must be worth it to them to lock it down and hope to see a device sold. Henry Ford said he'd give the cars away for free if he can be the only one to sell the parts. Vzw has aligned themselves closely with this mentality.
Sent from my locked Verizon s3
ancashion said:
If my x2 bootloader wasn't locked down like it is, ii wouldn't have purchased a new phone. Hardware is staying viable for a longer time than they would like, but, by locking down the software used they can obsolete your device long before the hardware is obsolete. Those who are savvy enough to hack it and put what they want on it also upgrade quick to the newest hardware for the wow factor and vzw knows this. Locking the device down prevents people like me from upgrading software easily, thus forcing a hardware upgrade- to achieve my desire for a software upgrade.
It's quite simple really. Phone sales. If any Joe-Schmoe could upgrade their droidx2 to jellybean, they wouldn't see that phone sale. No phone sale = no new 2 year contract.
They don't market the hardware specs at all like they market the OS.
It must be worth it to them to lock it down and hope to see a device sold. Henry Ford said he'd give the cars away for free if he can be the only one to sell the parts. Vzw has aligned themselves closely with this mentality.
Sent from my locked Verizon s3
Click to expand...
Click to collapse
This ^^^^^
I have the Verizon Samsung Fascinate that is running Jelly Bean better than some phones out now and this phone only has 384 mb of RAM and has been out for 2 years. Through the efforts of some of the best Devs out there, this phone has lived well longer than it should have (seeing as Samsung/Verizon only supported it up to GB). I've gotten the best battery life at almost 2 days of moderate usage, it's snappy, and still is getting support from the community, because of this I've seen no reason to upgrade other than to have the latest and greatest. A locked boot loader in their mind would prevent this. Keeping hardware, that could last well longer than 2 years, from keeping up with the latest software updates. But with the hard work of the Devs and the community, even with locked bootloaders we can still keep up with the latest (ex. Kexec for VZW GS3). I hope for an unlocked bootloader, but with the great Devs out there I'm not to worried. Waiting for my locked S3 to come in the mail and plan on rooting and customizing it how I want with kexec even with a locked bootloader. I do wish those who have messaged Verizon and Samsung the best of luck. But I won't be holding my breath for them, I'll be holding it for the great Devs and the great community.
CM10 on Fascinate
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lovely Battery Life
Sent from my SCH-I500 using xda premium
I have a fascinate as well from a while back when my wife had it. I've been strongly considering returning my s3 after I mod the fascinate like you have (since I've never done it before...) and rock it until something worthwhile comes out
Sent from my locked Verizon s3
I'm really hoping you guys get your bootloader unlocked but speaking from experience I don't think it will work. As you can see in my sig I have owned a lot of Moto/VZW phones and people were spamming FB and twitter and starting petitions and it never did anything. But I wish you luck that you can get somewhere with sammy because god knows VZW doesn't give a sh!t about there customers.
Author is xda member Ednylaw
To file with the FCC, EDNYLaw has created a formal complaint. To use, simply click the link below, download the .docx and input YOUR name and information required below.
http://dl.dropbox.com/u/26329079/FCC%20Complaint%20Web.docx
Here is EDNYlaw in his own words:
Quoted from Post 55: http://forum.xda-developers.com/showpost.php?p=29945914&postcount=55
EDNYLaw said:
I am the Attorney who wrote that comment on Droid Life and wrote the FCC Complaint. Please direct all your questions to me as I'm happy to answer them and help move things forward. A couple of things:
1) To those that think unlocking a bootloader is pointless with all the workarounds, I don't want to hear it, if that's how you feel, you're entitled to your opinion but please don't pollute this thread with your useless comments. Help or get out. PS: if the bootloader gets unlocked I fully expect either a) a statement from anyone saying it was pointless thanking the community if they choose to unlock or b) you DO NOT unlock your bootloader
2) I have not taken Verizon to court, the FCC did not take Verizon to court. The FCC made a determination that Verizon is violating the C Block regulation (it's a regulation, not law, there's a difference) and fined them. The violation was in regard to tethering apps and Google wallet. While my complaint touched on these things, the gravamen of my complaint was regarding locked bootloaders and custom ROMs, which I believe there is still a significant argument to be made.
3) Anyone who wants to read my full complaint (and send it to the FCC or their US Senators/Representatives under their name) it is located here: https://docs.google.com/document/d/109uYmho_6daIpAl0ACPSFoK0qrd6K9wp5yeqM7dEaoI/edit edit it accordingly as the beginning part was specific to me
4) Keep me informed and up to date about anything. The more minds the better. I've subscribed to this topic so I'll check in when I can.
5) As of yet I can't really think of a cause of action to take Verizon to court other than an injunction, but I'm not even thinking about a lawsuit unless it's funded or I get some help from other attorneys. I have a full time job and I'm learning to develop in my free time so I just don't have the time to pursue a giant lawsuit by myself for free right now
Click to expand...
Click to collapse
EDNYLaw said:
If OP could put this in the OP it'll probably be helpful:
When I say fill in your information I mean:
I've bolded the things you need to fill in
STATE OF YOUR STATE )
)ss:
COUNTY OF YOUR COUNTY )
----------------------------------------------------------------X
In re Verizon Wireless
YOUR NAME
Complainant,
-against-
Verizon Wireless
----------------------------------------------------------------X
You do not need an FCC Complaint Number, the reason I had a complaint number was I had previously sent in a complaint.
Make sure you also "sign" it at the bottom (last page) above where it says Complainant
Click to expand...
Click to collapse
Continued...
EDNYLaw said:
1) Use my complaint (provided in my post above) and in the first part where it says Verizon Wireless against... fill in your name and in the last part where it says "Respectfully Submitted" put your info in (Name, address, telephone, email)
2) I filed the complaint with the FCC and got a BS canned response from Verizon, I refiled and got the same canned BS response. After my Senator followed up I got a response from the FCC saying I could file a formal complaint, but clearly that was just a dead end since I filed 2 formal complaints and pushed the issue with my senator. Though I guess someone at the FCC caught wind because that 7/31 decision seemed to agree with my complaints and the timing was a little too coincidental
3) Completely free: go to fcc.gov and click on file consumer complaint. Email, fax or mail my complaint with your information filled in to them. I would also send it to your US Senators. Anyone from Minnesota, I think Senator Franken would be a great person to follow up with something like this.
4) In order to help out, SPREAD THE WORD! The more people that are vocal about this the better. When I was doing this with Moto I tried to get Droid Life, Android Central and Phandroid to post an article but none of them were interested. I say, spam them and get them to post an article with my complaint and what people can do. Again, the more people that are complaining and vocal, the more likely a response will be had. Give people my complaint to fill in, email the fcc chairman and commissioners (google to find their emails, it's just [email protected]). If you (or someone you know who is interested in this type of thing) is an attorney, feel free to PM me and maybe we can talk about something. Again, I don't have a tremendous amount of time to invest in this for no pay and by myself. But if there were enough attorney's interested I'd do it pro bono (for free) with the help of a group of attorneys.
And as I said, if you have questions about Verizon's policy and potential violations, ask me and I'll try to answer them. I did all the research and writing myself in my spare time and I think I nailed it insofar as the legal issues. There is next to no case law on the specific issues so I had to make legal arguments based on what little resources I had and the plain language of the regulation. Now at least that the FCC has released this decision, there is some precedent that they are actually willing to enforce a regulation instead of being a puppet for the wireless carriers (though I'm not completely convinced they're autonomous, 1.25 million to Verizon is nothing when their profits were 2.4 billion last year, that's .0005% of their profits for those keeping score at home)
Click to expand...
Click to collapse
Thanks EDNYLaw. Mine is going in the mail today!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Good bye HTC Rezound, hello Galaxy S3!
Haha this is epic. Here comes another fine Verizon!
Sent from my SCH-I535 using xda app-developers app
Dude I wish you well, and your kinda my hero today lol
Sent from my Xoom using xda premium
Very nice; thanks for posting it.
More momentum for our filing our complaints.
http://forum.xda-developers.com/showthread.php?t=1808956
FCC will win, VZW will send an update....right at the moment I say to myself, "Ah....it took weeks but I have my phone exactly how I want it!"
am i the only one who sees no reason for unlocking the bootloader? we have a perfectly functioning workaround.
brockkk said:
am i the only one who sees no reason for unlocking the bootloader? we have a perfectly functioning workaround.
Click to expand...
Click to collapse
Perfectly is an overstatement. It kinda sucks and we don't have a ton of development cause devs frankly don't want to deal with it.
Sent from my SCH-I535 using xda premium
We do have a good workaround, however we shouldn't need a workaround.
Hopefully this goes somewhere, and Verizon has to fork out some more of that money of ours.
What was the outcome of this letter? It was pre Nexus S, so I assume it's been dealt with?
brockkk said:
am i the only one who sees no reason for unlocking the bootloader? we have a perfectly functioning workaround.
Click to expand...
Click to collapse
Workarounds are a stop-gap, duct tape, a rubber band and bubble gum, and should be temporary. Many (myself included) don't want to deal with it and it isolates us from a significant part of the dev community. One of the reasons I wanted the SIII is for its large, wide-spread attention...but ours is gimped.
The bigger issue is that VZW won't stop at bootloaders; how long before they lock everything?
The biggest issue is VZW is doing an end-run around the law.
AndroidGraphix said:
Just read this and thought it would be nice to share.
http://www.google.com/gwt/x/e?u=htt...Ymho_6daIpAl0ACPSFoK0qrd6K9wp5yeqM7dEaoI/edit
Good bye HTC Rezound, hello Galaxy S3!
Click to expand...
Click to collapse
Where did you read that? Also, keep us updated!!!
ddggttff3 said:
Where did you read that? Also, keep us updated!!!
Click to expand...
Click to collapse
Found on Droid life.
Good bye HTC Rezound, hello Galaxy S3!
Drama queens. The development is fine.
brockkk said:
Drama queens. The development is fine.
Click to expand...
Click to collapse
The reason why we are "drama queens" is because Verizon is violating the law and is telling us that they could care less about that they locked the bootloader even if it violates the Block C since they can somehow get away with stuff like that.
brockkk said:
Drama queens. The development is fine.
Click to expand...
Click to collapse
Obviously a noob with no idea of the potential this phone has and how crippled it is with a locked bootloader. Either that or he is killing time until he can preorder the iphone 5.
Sent from my unlocked GTab 2 running CM10
This guy needs to talk to them about Google wallet. Stupid Verizon.
Sent from my SCH-I535 using xda app-developers app
Anyone know who the author is ??
the title is little misleading only cuz the fcc has not taken them to court yet, and more then likely Verizon will comply before it makes it to court
it looks more of very formal and will written compliant to the fcc (could be wrong still reading from phone)
very valid points presented in the compliant the fcc will diffidently pay attention to this one
i would suggest the author attache the petition in this thread to the complaint
http://forum.xda-developers.com/showthread.php?t=1756483
Sent from my Encrypted S3
Yeah, well. They claim that an unlocked bootloader shaves a few seconds off boot time. But it also has the ability to prevent bricks, and it makes development more open-ended. Right now all of vzw's custom rom devs have to bake kexec into the rom, which require extra work.
Sent from my SCH-I535 using xda app-developers app
To everyone saying that some people here are drama queens, look at all the development the international version has: http://forum.xda-developers.com/forumdisplay.php?f=1566. Just about all I see on that page is ROMs, ROMs, and more jelly bean ROMs. The locked bootloader has turned devs away from our version (as many people have already said). You may be happy with CM10 and a kexec workaround, but a lot of us want more options.
tonu42 said:
Look at how far whining has gotten for the Droid Series by Motorola. No where.
Click to expand...
Click to collapse
Did Motorola have an agreement with the FCC prohibiting such activities?
If it doesn't stop now, how long before your recovery also becomes locked?
kmoore11 said:
To everyone saying that some people here are drama queens, look at all the development the international version has: http://forum.xda-developers.com/forumdisplay.php?f=1566. Just about all I see on that page is ROMs, ROMs, and more jelly bean ROMs. The locked bootloader has turned devs away from our version (as many people have already said). You may be happy with CM10 and a kexec workaround, but a lot of us want more options.
Click to expand...
Click to collapse
International version had a jump on Verizon. Hell every other carrier did. I browsed the first page of at&ts development and counted 7 ROMs Verizon had 4 on their first page. And don't even bother looking at sprints development section. This is all getting blown out of proportion.
Greetings all...
You may be aware that verygreen is working on CM10 development for the 8.9" Kindle Fire HD. I am also working on getting this working on the Kindle Fire HD 7".
What works:
-Almost nothing so far. I can get past the bootloader and CWM will run (Thanks, verygreen!), but the CM10 ROM still needs to be developed further. I can flash it, and it appears to complete, but nothing comes up on the screen.
Trust me, this will be a slow process, but it IS BEING WORKED ON!
I will post any progress that I make.
::UPDATES::
[12/4] I now have screen working.
[12/5] Boots fully, but no touchscreen and the resolution appears to be wrong. (see image below.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[12/7] Touchscreen now works, but is off by 90 degrees.
[12/8] Basic functionality appears to be working now.
Wifi works, and screen and softkeys are all working now too.
Check out the video:
[12/10] 210 seems to be the magic DPI number for this device. Thanks to all of you who suggested that.
[12/18] Link to instructions on how to install revrom_alpha1:
http://www.reverendkyle.com/index.php/articles/177-how-to-install-cm10-alpha-on-kindle-fire-hd-7
Stay tuned...
Hi!
This is very good news!!!
Great work
As green has noted, the nexus 7 is a far superior deal, better hardware for the $, and is inherently unlockable by the manufacturer.
(Just wanted to note that in this thread for anyone considering a 7" tablet purchase. Go with open systems. The fire hd boot loader is now unlockable, but the next hardware may not be so easy.)
fattire said:
As green has noted, the nexus 7 is a far superior deal, better hardware for the $, and is inherently unlockable by the manufacturer.
(Just wanted to note that in this thread for anyone considering a 7" tablet purchase. Go with open systems. The fire hd boot loader is now unlockable, but the next hardware may not be so easy.)
Click to expand...
Click to collapse
I agree, the Nexus 7 is a better deal right now....
But once CM10 is running on the KFHD7, I bet it'll give the N7 a run for it's money. Plus, you know there are going to be a million people (exaggerated) who want to load up their KFHD7 with CM10, so someone has to make it happen.
Oh, and just so everyone knows.... I have a Nexus 7 too.
good to hear it's going to happen on the 7" variant. Can't wait. :fingers-crossed:
nice bro
Sent from my SGH-T989 using xda premium
Do you use Hashcode's Safetrap tool?
As i known, CWM can't support 7'HD Kindle Fire now.
padest.com said:
Do you use Hashcode's Safetrap tool?
As i known, CWM can't support 7'HD Kindle Fire now.
Click to expand...
Click to collapse
No.
Now that we have the ability to unlock the bootloader, Safestrap becomes unnecessary.
Yeah don't get me wrong... I'm all for developing alternate oses for formerly locked devices, if only to demonstrate how futile and immoral (for lack of a better word-- dickish is another) it is to try to lock people out of their own devices. . but why buy them to begin with if there are better options?
Sent from my Nexus 4 using xda app-developers app
fattire said:
Yeah don't get me wrong... I'm all for developing alternate oses for formerly locked devices, if only to demonstrate how futile and immoral (for lack of a better word-- dickish is another) it is to try to lock people out of their own devices. . but why buy them to begin with if there are better options?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Because people like having a choice. From everything I have seen and read, the physical quality of a nexus 7 left a lot to be desired. I like the speakers and screen on the kindle hd better. I am tied up to Amazon ecosystem. So many reasons. It's a sad world when people only want you to buy one thing. Competition is good for everyone. The original kindle fire is the entire reason the Nexus 7 came to be at that price.
Not to mention, that no matter how many people you tell fattire, they aren't all going to go out and return their kfhd, and buy an N7. It would be like me going around the nexus 7 forum, and telling people that the kfhd has a way better screen and seems to be a better buy. When you post useless comments on these forums, it certainly isn't helping get anything done:these threads don't need to be arguments.
Sent from my Fire HD with root!
Very excited for this! If you need any support/testing let me know. I love CM10 on my phone.
craby1925 said:
Not to mention, that no matter how many people you tell fattire, they aren't all going to go out and return their kfhd, and buy an N7. It would be like me going around the nexus 7 forum, and telling people that the kfhd has a way better screen and seems to be a better buy. When you post useless comments on these forums, it certainly isn't helping get anything done:these threads don't need to be arguments.
Sent from my Fire HD with root!
Click to expand...
Click to collapse
If it were true that the KFHD 7" were a better buy, then by all means anyone should say so in any forum. I'm not going to modulate my opinion because I'm in the KF HD forum. The facts are the facts. Although the build quality of the N7 is great, I wasn't talking about screen quality. I was focusing on something more fundamental-- the locked bootloader bug, which comes with every KFHD.
Without escalating this too much, I don't think our posts pointing to this bug are "useless"-- not everyone here has made a decision on what 7" device to buy yet. While the bootloader being unlocked comes very easy and quickly for you and seems to be taken for granted, poring over uboot code and finding and/or creating fixes is a lot of extra and IMO unnecessary work that could be better spent on other, more useful things.
I am tied up to Amazon ecosystem.
Click to expand...
Click to collapse
EXACTLY!
It's a sad world when people only want you to buy one thing.
Click to expand...
Click to collapse
That's precisely the problem with the locked bootloader. It's a power grab, an attempt to lock you into using only one OS, and buying only through one company. And so, without a bootloader fix, you're stuck with a single OS, without access to source code, as you are tied to their services more and more. You said "I like having a choice." Well, it's not a free system out of the box; it severely limits your choices, and that matters. As far as 7" prices go-- credit the KF all you like, but do remember the KF was an unlocked device. (Also, the 7" Nooks, ultra-cheap android tabs, and the Play Store deserve credit too, but I'll leave this for another discussion.)
Anyway, we've said our opinion. The readers can take it or ignore it.
Okay, it boots. Touchscreen not working, and resolution appears to be off.
I'll add this to the OP as well.
Not to derail a thread for CM10 dev, but I thought I should weigh in so that fattire doesn't look like a complete a-hole.
I totally agree with his sentiment of "dev's cannot keep spending their time opening devices which are locked." Consumers need to understand this isn't a "given". Finding exploitable code takes weeks by a dedicated dev who does it for free. And is only getting harder. There will be a time in the not so distant future where locked bootloaders will be perfected. The only way we can tell vendors that this is wrong is by not buying their products. (However futile this may be -- see my reasoning near the end)
I also disagree on a few minor points which are more specific to the how/why we end up with these devices and the economics of ecosystems.
* We get these devices as gifts. And for various reasons we don't really want / can't return them.
* We end up with less than usable devices when we move into areas that aren't as desirable (IE: international use of Kindle's can be tough in Amazon's ecosystem)
Which makes for users wanting to install a new OS like CM10 or another variation of AOSP.
Amazon makes money on the ecosystem usage. Not from the tablet sale. So just the act of buying it isn't going to score a huge payoff for Amazon. It's more to do when you buy the books, movies and apps from their stores. If everyone bought a KFireHD and then unlocked and put CM10 on it. I think the message to Amazon would be: your ecosystem needs work.
Lastly, consider the # of users who have modded their 1st gen KFire's with a new OS. Now take that # (I'd guess it's in the 40k range) and match it up with the millions who bought them. From a practical stand point that kills the "Don't buy their products until they unlock them" argument. But it's still the right thing to do if you are the kind of user who wants to change their OS. Don't buy a locked device and then hope to be rescued later by a dev.
Perhaps we can sort of agree to disagree on some things, and let this thread continue.
EDIT: Grats ReverendKJR
I think hashcode said it very well. I know a lot of dev types who refuse to contribute at all to locked devices on principal or because it's a hassle... But I (obviously I hope) think these broken devices *should* be fixed and alternative oses made available lest it appear locking bootloaders are an appropriate or successful strategy (ie , capturing and locking in customers vs. keeping their business on the merits)... Although there are security/privacy/performance/compatibility factors too) My earlier comments and i think greens too were directed to those considering a new 7" purchase.
Nice work, rev.
jacewt said:
Because people like having a choice. From everything I have seen and read, the physical quality of a nexus 7 left a lot to be desired. I like the speakers and screen on the kindle hd better. I am tied up to Amazon ecosystem. So many reasons. It's a sad world when people only want you to buy one thing. Competition is good for everyone. The original kindle fire is the entire reason the Nexus 7 came to be at that price.
Click to expand...
Click to collapse
I suppose it comes down to priorities, but for many users here an unlocked bootloader is important. The suggestion that folks buy the Nexus 7 isn't contradictory to competition. In fact, the suggestion to buy the Nexus 7 is an exercise of buying from the competition, in part, to voice an opinion that unlocked bootloaders are important.
Locking the bootloader must have a negative financial impact on a company in order for them to leave their devices open.
For me, the trend of locked bootloaders and losing device control goes beyond simply impeding my recreation. Its a matter of security and getting my monies worth from a device.
Keep in mind the people in this thread suggesting to buy an open device are the very same people that are responsible for spending their time and money to unlock the closed devices. This should, at least in some way, give their opinions some weight.
reverendkjr said:
Okay, it boots. Touchscreen not working, and resolution appears to be off.
I'll add this to the OP as well.
Click to expand...
Click to collapse
Nice work so far. I agree somewhat with what others regarding purchasing locked devices however I think there is something attractive about tinkering with something that a manufacturer told you they don't want you tinkering with.
That being said, I won one in a drawing and it should arrive this week or early next. I might be willing to do some testing if you need it at some point. Let me know what I can do to help.
Great progress, so I believe we can agree to drop the subject with no further discussion? Very good than.
Sent from my EVO using Tapatalk 2
reverendkjr said:
No.
Now that we have the ability to unlock the bootloader, Safestrap becomes unnecessary.
Click to expand...
Click to collapse
Thanks！
I wonder to see your CM10!!!
BTW, how can we unlock the bootloader? Just like this???
1. use "adb reboot bootloader" access to fastboot mode?
2. using "fastboot oem unlock"
"In the years of Jan. 2016,SAMSUNG will be take a Realase Conference to introduce a new model Galaxy S7" this news was release from the High technecial Channel.
According to the latest news,The flagship galaxy S7 will come with three version,the size of panel digizter will be 5.2inch、5.8inch and curved screen,the most improtance that the camera will be utilization with 20,000,000 pixels,will come with dual front camera?as for this theme, i suggest you to contact the official for a truth.but hear about a third -class media,it's said that samsung get a big truoble about the compatible issues bettwen USF2.0 and TFT extend cards.
However,as a proverb d said,love me love my dog.how many guys hates this brands,and there will be many guys fond of it.to our fans,the most exciting moments is coming,samsung will utilization three types CPU Processor in the three most improtant market,China and US will come with Qualcomm Snapdragon 820，EU、South Korea and Japan will come with Exynos 8890,the third party is India,which will come with Exynos 7422.Besides all above the previous,galaxy S7 will support ClearForce Touch,which will be more function and strongth than 3D Touch,like support Gallery Edit,Capital control,Symbol Selection etc.ClearForce Touch will utilization the double click methods,like the action of click the right mouse.when you paintting,it's support the thickness control of the pen touch.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you fond of the smartphones,i suggest visit http://www.devicespecifications.com
What a nice design
can't wait for it
Seems really interesting.
Lähetetty minun A0001 laitteesta Tapatalkilla
stevenangkasa
stevenangkasa said:
What a nice design
can't wait for it
Click to expand...
Click to collapse
yeah,it's might be release in few months later.
A0001?i had nerver hear about of this model.
A0001 is the model name for ONEPLUS ONE...LOL
Very interesting ... waiting egarly for it. I heard somr rumors that Samsung is going to launch it in Jan 2016 . 3 months before its usual launch. Is it true..
Can't wait
Sent from my SM-N910T3 using Tapatalk
yes,i had hear about the same news too.
getbizzin
It's appears that you are fond of Note series,why don't you consider about Note 5?
My question is are they going to bring back mSD support?
I really couldn't care less about having a uniframe or metal body if it sacrifices having a mSD slot available. Not to mention the availability to simply swap out a dead battery with a fresh fully charged one.
What's more frustrating is this isn't an issue that requires too difficult a fix to be reasonably implemented. Plenty of other devices have or had spring loaded dot release slots for sd cards as well as simple cards.
A mSD slot is no more vulnerable to issues than a micro usb is. They already ditched the water/weather proofing feature, so that isn't the reason.
Unfortunately, it would seem like they're struggling to find fresh design that host an advancement of the previous generation's features. Instead, we're regressing in utility and technical capabilities in the name of aesthetic appeal (?), I guess?
I, like 95% of the people of earth with a smartphone, keep a case for its protection at least about 90% of the time. The backing of the phone is squarely at the bottom of the list of things to look for in my future purchases.
Ya know what would be really cool? A phone that is glass on the front (screen) and back. Oh yeah, they did that and everyone ended up needing a fancy rubber band slapped around it to keep the antenna from doing its best impression of your old school bunny ears TV antenna, essentially worthless.
A "smart" device such as a mini computer we cutely refer to as a phone must bend form to its function. A car built on the premise of using square tires is going to be a disaster.
I'm not the only and hardly the 1st to voice their displeasure, but what's changed?
Something huge, actually. We're beginning to see an official policy change straight from the top with respect to mSD, or additional storage in general. Google themselves have seen the writing on the wall , and in a full turnabout, the latest dessert offerings from the Android mothership include a host of expanding features and core implementation dealing with greater cohesion of the OS's abilities and use of added storage.
I could go on, but the point being is that something has to give, and I don't think Samsung holds the high card. The largest phone manufacturer for android just dropped SD support in all their new flagship phones. Yet, Google is about to go big into unleashing the use and integration of external memory. Their previous view on the subject is clearly spelled out. All you need to know is that every Nexus phone - Google's self anointed phone for "pure" android, has NEVER had a model with the ability to add additional external storage.
Next year's Nexus will almost certainly be the first to include it.
Hence, I ask, what's the word on Samsung reintroducing mSD support, because I'm almost positive that Samsung will be the first to blink on this subject.
This device won't really impress me much UNLESS Knox is disabled by default. (Not just app I mean in the boatload) and its unlockable. Why doesn't Samsung see that NO ONE LIKES KNOX. (No one in this community anyway) its straight up a pain in the ass for developers. I really REALLY want this to be a good device, but I wait unimpressed BC the s6. There's my rant. -pronax on the nexus 6
pronax said:
This device won't really impress me much UNLESS Knox is disabled by default. (Not just app I mean in the boatload) and its unlockable. Why doesn't Samsung see that NO ONE LIKES KNOX. (No one in this community anyway) its straight up a pain in the ass for developers. I really REALLY want this to be a good device, but I wait unimpressed BC the s6. There's my rant. -pronax on the nexus 6
Click to expand...
Click to collapse
KNOX isn't aimed at this type of community, the app itself was originally designed for corporate use designed to protect data with a 1-click "job done" type of mechanism. The issue is that the idea was never really adopted among consumers, besides getting rid of KNOX isn't so hard. As long as a phone has cool mechanisms in which it makes it unique, you can't call it a bad device just because it has specific software pre-installed.
Seems a cool gadget... But seems weird to me as it's not long ago since the launch of s6 and s6+....! And if at all Samsung is planning something like this then it will be a big surprise!
True but the average person doesn't really need Knox. For big corporations, yes, I see how it can be useful I totally understand. I'm saying the bootloader should be unlockable. Maybe a switch in dev settings? I'm referring to the almost uncrackable bootloader and the knox counter not the app.
pronax said:
True but the average person doesn't really need Knox. For big corporations, yes, I see how it can be useful I totally understand. I'm saying the bootloader should be unlockable. Maybe a switch in dev settings? I'm referring to the almost uncrackable bootloader and the knox counter not the app.
Click to expand...
Click to collapse
I think the idea is to make the phone secure. 99% of users don't care if it's easy to root or not. They care if their data is secure. They care whether the thief who steals their phone can access their personal or corporate information. The harder they make it for people to modify or break into the phone, the better their sales will be. They don't cater to us, they cater to the masses who buy their phones.
Theodric58 said:
I think the idea is to make the phone secure. 99% of users don't care if it's easy to root or not. They care if their data is secure. They care whether the thief who steals their phone can access their personal or corporate information. The harder they make it for people to modify or break into the phone, the better their sales will be. They don't cater to us, they cater to the masses who buy their phones.
Click to expand...
Click to collapse
I don't think your getting my point. English is not my maiden language so excuse please for any spelling mistakes. But I am speaking of the warranty counter in the bootloader (Odin) mode. I do not think that should be there. Ah well you all seem to think I'm off base here. So I will stop commenting
pronax said:
I don't think your getting my point. English is not my maiden language so excuse please for any spelling mistakes. But I am speaking of the warranty counter in the bootloader (Odin) mode. I do not think that should be there. Ah well you all seem to think I'm off base here. So I will stop commenting
Click to expand...
Click to collapse
Never stop commenting.
They have the KNOX counter because their warranty specifically states they are not responsible for any changes we make to our phones. As far as they are concerned, changes you make to the root software can negatively impact the phone. From the Warranty listed on their website for my Verizon S6:
"(g) defects or damage resulting from improper testing, operation, maintenance, installation, service, or adjustment not furnished or approved by SAMSUNG, including but not limited to installation of unauthorized software and unauthorized root access, both of which shall void this limited warranty."
That's why they have a KNOX counter. It would be nice if there was a way that we could just say "I don't care about the warranty, let me root my phone." But since there are root methods that can not trigger KNOX....
Theodric58 said:
Never stop commenting.
They have the KNOX counter because their warranty specifically states they are not responsible for any changes we make to our phones. As far as they are concerned, changes you make to the root software can negatively impact the phone. From the Warranty listed on their website for my Verizon S6:
"(g) defects or damage resulting from improper testing, operation, maintenance, installation, service, or adjustment not furnished or approved by SAMSUNG, including but not limited to installation of unauthorized software and unauthorized root access, both of which shall void this limited warranty."
That's why they have a KNOX counter. It would be nice if there was a way that we could just say "I don't care about the warranty, let me root my phone." But since there are root methods that can not trigger KNOX....
Click to expand...
Click to collapse
Yes the point you bring up is a very interesting one because the KNOX counter appearing 0x0 still after root. A custom recovery would be nice for all kinds of reasons but I can't for see it happening. I still think their unauthorized policy thing is too strict. Because of not being able to use the phone. I'll use example of "software not authorized by Verizon..." Because that was just dirty. If it said hello your warrenty is now void but you can still use the phone I think that would be fair. I do reaise that warrentys are expensive and people like them
Anybody interested in the bootloader and unlocking it I encourage you to sign this petition. These phones are ours to use how we see fit and the more noise we make the better our chances are. I bought this phone under the assumption that nothing had changed and for Samsung to change their policies without notice isn't acceptable for me and hopefully you as well. Thank you
Petition
And please re-tweet:
Vote which John
It's time!
I signed
Used the picture on Instagram and @JohnLegere thanks!
lost_ said:
And please re-tweet: It's time!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Done!
Sent from my SM-G935T using Tapatalk
Signed!
Signed
Signed.
This bad boy has over 500 signatures now. The more we share and retweet the louder we sound. Samsung has also responded to a few people, so you know we're being heard. Keep your fingers crossed and keep the pressure up until we hear one way or the other.
See, this is what is wrong with this picture... "Make Tmobile great again"! That's wrong, Tmo has been doing a great job as of late; do not undermine its performance just because Sammy is putting all of its panties in a bunch with their pay system.
That picture should have said "Keep Tmobile being great"! If I was the CEO of a company and I come across something like this, I would be losing respect for whatever movement faster than ligth because it is making me look bad not just the company.. especially if it has not been proven that Tmo is at fault here guys; don't paint as a bad guy an innocent party until proven guilty.. It defeats the purpose
Signed
Signed!
signed! git 'er 'dun T-Mobile!
brendan802 said:
Anybody interested in the bootloader and unlocking it I encourage you to sign this petition. These phones are ours to use how we see fit and the more noise we make the better our chances are. I bought this phone under the assumption that nothing had changed and for Samsung to change their policies without notice isn't acceptable for me and hopefully you as well. Thank you
Petition
Click to expand...
Click to collapse
What percentage of people do you think own the phone vs lease the phone? I would wager the vast majority are using it on JUMP or JOD or just a regular lease. If you are leasing a phone, its certainly "not yours to use how you see fit". It would be great if Samsung would allow those of us who paid the phone full price the option to unlock the bootloader, but T-Mobile is under no obligation to do it for those who lease the phone.
Signed
Sent from my SM-G935T using XDA Free mobile app
Semantics said:
What percentage of people do you think own the phone vs lease the phone? I would wager the vast majority are using it on JUMP or JOD or just a regular lease. If you are leasing a phone, its certainly "not yours to use how you see fit". It would be great if Samsung would allow those of us who paid the phone full price the option to unlock the bootloader, but T-Mobile is under no obligation to do it for those who lease the phone.
Click to expand...
Click to collapse
Your name is very accurate.
Also, you seem to be, at core, a very self-centered, self-serving individual. Why would you even present that argument, when an unlock for everyone gives you exactly what you get if your suggestion is implemented? Do you have a need to be one of the only ones with the full bells and whistles? Is it a need to be the cool kid with the rooted phone that no one else has? Is it because you feel more entitled, as you bought the phone outright for reasons of your own, instead of going on month-to-month? I'm genuinely curious, none of this is meant to insult you. I'm interested in the psychology behind people who see things like you did.
psych0r3bel said:
Your name is very accurate.
Also, you seem to be, at core, a very self-centered, self-serving individual. Why would you even present that argument, when an unlock for everyone gives you exactly what you get if your suggestion is implemented? Do you have a need to be one of the only ones with the full bells and whistles? Is it a need to be the cool kid with the rooted phone that no one else has? Is it because you feel more entitled, as you bought the phone outright for reasons of your own, instead of going on month-to-month? I'm genuinely curious, none of this is meant to insult you. I'm interested in the psychology behind people who see things like you did.
Click to expand...
Click to collapse
I've said already I'm not rooting regardless. I find it ironic the guy who doesn't actually own his phone feels that he's entitled to the same benefits as the people who actually do own the phone. If you want to use words like it's mine to do as I please, then you should at least own the phone before claiming ownership. I couldn't care less about an unlocked bootloader, its clearly an issue for some, but don't try and play me as the entitled one when you are in fact acting like you are owed something you are not. Bernie Sanders fan too I wager.
Semantics said:
What percentage of people do you think own the phone vs lease the phone? I would wager the vast majority are using it on JUMP or JOD or just a regular lease. If you are leasing a phone, its certainly "not yours to use how you see fit". It would be great if Samsung would allow those of us who paid the phone full price the option to unlock the bootloader, but T-Mobile is under no obligation to do it for those who lease the phone.
Click to expand...
Click to collapse
Id say that probably about 25-30% own them outright and I understand what you are saying but they use to be unlocked no matter what method of payment you have so why should that change now? If they would unlock just the ones sold outright that would be fine for me and I bet that would be better for the carriers too. Either way they shouldn't change their stance without notice as samsung knows how upset people become over locked bootloaders. I am with sprint for the record as t-mobile isnt available in fabulous rural rutland vermont and I posted to all carrier forums hoping the more noise we make the better for us all.
A promising lead or empty words from a Tmo employee: Real or Not?
Edit: TMobile deleted the tweet by KimB that stated, "it's getting unlocked.."
Semantics said:
What percentage of people do you think own the phone vs lease the phone? I would wager the vast majority are using it on JUMP or JOD or just a regular lease. If you are leasing a phone, its certainly "not yours to use how you see fit". It would be great if Samsung would allow those of us who paid the phone full price the option to unlock the bootloader, but T-Mobile is under no obligation to do it for those who lease the phone.
Click to expand...
Click to collapse
psych0r3bel said:
Your name is very accurate.
Also, you seem to be, at core, a very self-centered, self-serving individual. Why would you even present that argument, when an unlock for everyone gives you exactly what you get if your suggestion is implemented? Do you have a need to be one of the only ones with the full bells and whistles? Is it a need to be the cool kid with the rooted phone that no one else has? Is it because you feel more entitled, as you bought the phone outright for reasons of your own, instead of going on month-to-month? I'm genuinely curious, none of this is meant to insult you. I'm interested in the psychology behind people who see things like you did.
Click to expand...
Click to collapse
No Im not doing this just for myself I strongly believe that android should stay open the way its meant to be and locked bootloaders are not that. And actually guess what I'm on a month to month lease with sprint but if need be I will go out and buy one outright so I can do what I want with something that is supposed to be mine. Hows that for self serving because I wouldn't get the unlock if they released it right now to paid in full s7 owners. Were you expecting that I bet not. I have never had a single device whether I bought it outright or not that had a locked bootloader and I wont keep one that cannot be unlocked. Douchebag looking to start sh!t with a stranger real nice you dont know me or what I'm about. 24 payments of $30.50 but Im self serving like you thought. No response from the psychologist huh. You know samsung had previously locked phones that they sold as developer editions if you bought them outright just like I said paid in full. I think that none should be locked no matter what way you pay for them. Its like saying if you are paying off a car that you cant put a performance pipe on it because you haven't paid it completely off???
Here is my lease agreement
https://onedrive.live.com/redir?res...authkey=!AGpsyhp_4N0lMyg&v=3&ithint=photo,png