• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Our Rights!!!

But it can generate revenue, and possibly be very lucrative. It would stop the people who like to flash back and forth on a whim, but I wouldn't have any problem paying $25-35 for a rom I liked.

As far as the trojan thing goes, if a dev does it the manufacturer would not be responsible if they did due diligence in checking out the rom. And a rom screwing up someones phone would not happen under what I have proposed, no overclocking or running beyond factory specifications would be allowed.

As far as John and Joan Public, imagine a boutique style display at the local cell carrier with choices of how you plan to run your phone; want something optimized for business, we can do that; heavy text and email customer, go with this rom; dull Bob, how about plain vanilla: want to tinker, look at this multi-rom subscription package.

The fact is, this is a very good scenario that could be profitable for the manufacturers and carriers while benefiting the customer as well, and that is how business is supposed to work, keep everybody happy.
 
Lots of sub-threads and thoughts among the thread. Rather than quote all of them, here are a few thoughts. Agree or not, corrections are welcome.

Human rights. I really do not think that your not being able to change icons or more easily install a custom ROM is a human rights violation issue. Lets not start talking about our issues and irks as human rights violations. It helps dillute the meaning of the words and that is dangerous.

Members like Stinky actually do know and understand well, what a human rights violation is and perhaps he (and others) take offense at making the sad comparison. Just saying, STOP with that comparison because it bespeaks of one's ignorance.

Our 'rights.' Someone asked about the manufacturer's rights. So I'll ask again. Manufacturers do have rights and one of those rights is perhaps to keep the phone "locked" to prevent people from screwing up the phone then begging for free repairs.

The contract you sign lists their rights or perhaps responsibilities and duties and it lists your rights. You have a right to expect that your phone works as advertised, connects to the web, deals with email, install apps, etc. You do not have a right to change components within the product or modify it in such a way that it might cause technical problems.

And firmware is a component even though it is software.

And let's face it, most people do not have ANY IDEA about programming, hardware, or how one small change can affect their phone. They root their device and install something not designed for their phone, like one person I read about that rooted his phone, could not find the proper ROM, so he guessed and installed a wrong one.

That foolish person deserves a bricked phone and zero warranty service.

It really does not matter what one thinks their rights should be. They signed contracts and before crying, perhaps they should take a look at their agreement. Just because we think the written agreement is bad or unfair, we must follow it, agree to it, and stop complaining. Do not like it? Well, buy a different phone.

Do you have the right to change the firmware that controls your HDD? Yes, perhaps you do. It is your drive, after all. But when you screw it up, should the manufacturer pay for your lack of knowledge and skills? I assume disk drives have firmware of some sort. OK, then your BIOS, that is upgradeable.

I am not sure there are any rights violations going on; the rights you have are written, so take a look.

I DO AGREE that bloatware is an issue. I hate it and I wish I could rid my phone of it. It likely does me no harm and if that is true, I have no case in court. I despise UNO and Midnight Bowling, too.

Removable parts were briefly mentioned. I have considerable experience in the consumer electronics manufacturing business and it is a difficult thing to make changes like going from SMT components to socketed parts. In some cases, you need additional production workers to insert the parts by hand. All it costs is more money and there is ZERO benefit.

If the consumer does it, I see disaster due to ESD issues and the like.

The PCB (Printed Circuit Board) would require redesign to accommodate sockets. Traces or connections between components do not just sit on the surface or reverse side of the board; connections between parts exist in multiple layers. And some boards can have more than five layers, so adding a socket that requires more space requires a redesign.

Sockets would require that the phone be designed that way from the beginning.

Adding a socket is hard and not only will it increase the size of the PCB, it will require a redesign and retooling of the case as well. Because it is now thicker. Sockets loosen, chips come loose, and phones stop working. More repair costs, and ultimately, higher consumer costs. So sockets will never be used in great quantities because SMT is simply cheaper.

If the consumer wants to change the IC, he or she needs to open the case. So you might end up with a costly product if the manufacturer decides that the physical ROM/IC/Flash/Whatever should be changed by the carrier /manufacturer rather than a fumble fingered consumer that has no business taking apart and disecting a complex littloe fella like an Android.

You going to send your phone in every time you see a cool new ROM or the carrier makes an upgrade? Assuming the carrier can make repairs in the first place; it might need to go to the manufacturer or a service station.

Some parts like ICs are BGA components. This is Ball Grid Array and they are designed to be soldered to the PCB. Impossible to change and tricky to socket.

So we are left with flashing which is likely how the manufacturer/carrier got the software into the product in the first place. Quite likely because updates are currently handled via OTA. And since it is "easy" to root using software, why redesign a product to use replaceable ICs, or sue a manufacturer to do something that can be cheaply done with software that only by a handful of people give two hoots about in the first place?

Law Suits: Not bloody likely. No way a class action will be certified by a judge because it is just silly. You are not harmed materially, and this is something YOU ABSOLUTELY NEED TO DO. So no reason to sue and no basis for the suit. Just wasting everyone's time for something that will never happen.

Most here likely cannot pay for a class action lawsuit anyway. Lawyers will likely take the case "For Free" only if they see a payday. Pissed off, then write a letter or start a petition.

So this is my idea: if you want to sue or whatever, start by getting the carriers to provide phones that are open and no need to root. I do not think you stand a chance in heck, but go with God, and luck to you. The last thing they want is to start seeing thousands of phones returned because the user is a fool and is playing around in areas he has no business in.

Then you can delete the crap you do not like (some people might actually like some bloatware) and be done with it. No reason to drive the costs for most of us up to satisfy the bitter views of a unmeasurable minority.

If this crap we do not seem to like does cost us money because it does this and that behind the scenes as one poster suggested, then yes... we have a case because I was not told some software I can't delete is costing me money.

Root Access: when I jail-broke my new iPad, I installed a file manager. As someone who is unclear as to the files that are needed and where the the crap-ware was buried in the file system, I asked a forum member for help. I was told that yes, you can delete the app (Apple's Game Center) but parts of that app run all through the system. So apparently I can never get rid of the thing. I simply hid the icon and was done with it.

My point is, any tech service wonk will tell you that people often delete crap that should leave the hell alone, and sometimes, it screws up their system. They simply do not know squaddle and perhaps it is good that the typical phone user be prevented from root access.

Bob Maxey
 
Bob, if you read the whole thread you hopefully saw my reference to "rights" in the title was nothing but an eye catcher, I don't think any kind of human rights violation is going on here. I do see the very real possibility of a consumer rights issue, but that applies only to the bloatware. It does not have to run in the background and cost money to be an issue. The fact that it can tie up system resources on a product I purchased and own, not leased from the carrier, and is not a necessary component of the operating system then I am being forced basically under duress to accept an app that I neither want nor will ever use to be able to have the phone of my choice. All of this under the guise of being a "system app", which it is not! And the argument others have made "if you don't like it get something else" totally misses the point! That basically admits that choice is taken away, if I don't like the bloatware on the phone of my "CHOICE" then I have to make due with something else, which may or may not fill the need my original choice was capable of.

I can not speak for anyone else posting here, but my proposal does not advocate free run flashing of whatever rom you see fit. I am suggesting a cooperative plan between the manufacturer and carriers to offer a choice of roms, whether they develop them or allow devs to submit their roms for review and approval, providing they run within hardware specifications so there is no issue with a rom over-stressing hardware to the point of failure. They would also have the right to void your warranty if you fail to follow instructions and brick your phone during the flashing process which is really hard to do, you can still reload or run an ruu unless you screw up your recovery. And the carrier can offer a service to load the rom of your choice in shop or ota, thereby bypassing that possibility while making money.

I would like to see a voluntary adoption of the bloatware removal and rom program, but if that is not going to happen, I would like to see at least the bloatware issue addressed through legal or legislative means.
 
Bob, if you read the whole thread you hopefully saw my reference to "rights" in the title was nothing but an eye catcher, I don't think any kind of human rights violation is going on here. I do see the very real possibility of a consumer rights issue, but that applies only to the bloatware. It does not have to run in the background and cost money to be an issue. The fact that it can tie up system resources on a product I purchased and own, not leased from the carrier, and is not a necessary component of the operating system then I am being forced basically under duress to accept an app that I neither want nor will ever use to be able to have the phone of my choice. All of this under the guise of being a "system app", which it is not! And the argument others have made "if you don't like it get something else" totally misses the point! That basically admits that choice is taken away, if I don't like the bloatware on the phone of my "CHOICE" then I have to make due with something else, which may or may not fill the need my original choice was capable of.

I can not speak for anyone else posting here, but my proposal does not advocate free run flashing of whatever rom you see fit. I am suggesting a cooperative plan between the manufacturer and carriers to offer a choice of roms, whether they develop them or allow devs to submit their roms for review and approval, providing they run within hardware specifications so there is no issue with a rom over-stressing hardware to the point of failure. They would also have the right to void your warranty if you fail to follow instructions and brick your phone during the flashing process which is really hard to do, you can still reload or run an ruu unless you screw up your recovery. And the carrier can offer a service to load the rom of your choice in shop or ota, thereby bypassing that possibility while making money.

I would like to see a voluntary adoption of the bloatware removal and rom program, but if that is not going to happen, I would like to see at least the bloatware issue addressed through legal or legislative means.

I did read the thread and my reply was an attempt to comment on a number of different ideas. One such thought was the mention of Human Rights and several people commented. I simply wanted to remove that idea because this issue we are discussing has nothing to do with human rights.

And I agree with you. We should be allowed to delete stuff we do not want. I would support that initiative because these apps take up space and I hate looking at them. It might take legal action or a letter writing campaign to get it done. I definitely support it unless it causes our costs to rise.

Are these unwanted apps a revenue source?

I have no problem with ROMs. Let the consumer decide. Full warranty for approved ROMs and iffy warranty service for non approved ROMs. Matters little to me because I just need a basic set of services.

Cheers,

Bob Maxey
 
Yes Bob, some are a possible revenue source from add content, others are considered a "value added service", the only other possible revenue is for data overage if you don't have an unlimited plan (and I don't understand why anyone who would use these apps would not have one).

Prime example though, I couldn't give a flying flip about the NFL app, care even less about the Nascar app and have only watched Sprint TV once when I had my Hero. The only app I have used is Sprint Navigation and Google Nav has made that obsolete now. I guess they are getting their add revenue whether I use the apps or not, but if I am not using them why do they have to continue to take up room on my phone? Does Sprint think I will eventually break down and say "Hey, it's here, might as well use it"?

Maybe we should start an e-mail campaign. As I said before, approach the other forums and try to increase our numbers and bomb the carriers e-mail account with protests. If we are successful there we can move on to the rom issue, or do it concurrently.
 
Don't apologize until you do something wrong. :)

Actually, a few years back some bright guys came up with the idea of open phone hardware and a special Linux system with Python programming to go with it.

I was all for it and some days still can't stand that it didn't really pan out.

When Android came along many of questioned what this was all about because we already had a project to do a better Linux phone and open hardware to boot.

That project lost, Android won.

The name of the project is OpenMoko - Open Mobile Communication - and they're still plugging away at the idea:

Openmoko, Inc.

Openmoko, Inc. | FreeRunner

Main Page - Openmoko

I first heard about that like 5 years ago back in a magazine..

It was incredible..

Shame they didn't have an "end user ready" version because, i would have jumped on it..

Nokia also had the N series which was geared towards open source.. n810 stands out the most as predecessor to the n900

which were also spawned by the openmoko
 
I first heard about that like 5 years ago back in a magazine..

It was incredible..

Shame they didn't have an "end user ready" version because, i would have jumped on it..

Nokia also had the N series which was geared towards open source.. n810 stands out the most as predecessor to the n900

which were also spawned by the openmoko

This would have to be a dabbler slash fiddler slash hacker product because the general public will never want a build it yourself phone. Hell, the average person really does not know how to solder, much less about the dangers of ESD.

But, as with all technology, the market determines if it lives or becomes an also ran.

Bob Maxey
 
Warranty work is a very tricky subject. When it comes down to it its your word vs. Theirs. How many owners can say they are experts in their item they want warranty work done on? I look at it this way. If you mod anything from its stock beginnings. It ceases to be the item the warranty covers.

People complains about consumer rights but what about manufacturer rights? Why should they foot the bill for someone that fries their phone from oc it? What ever happen to I take responsibility for our actions? When we play with our toys hard don't they break in the end sooner than the manufacturing says? .

Root your phone that's fine, mod your car that's fine. But when it wears out from your tinkering you are the one that should foot the bill.

And . . . read your agreements and the little book that came with your phone. You might be expressly forbidden from doing anything with the device. You can argue it is not fair, I should be allowed to do this and that, but I think the manufacturer/carrier has some rights, too.

Bob Maxey
 
@ copestag

And who's talking about bloated firmware thats a problem anywayz? Yes it is destructive but it doesn't matter actually:

IF everything was modular / replaceable then you could just replace the ENTIRE whole damn EPROM / ROM urself and put what ever operating system you want on there anyway without the worry for bloatware so that's the end of that discussion... anywayz... i have my point of view and it won't change unless i am givin good reason to change my point of view.

Anywayz...

Well, assuming the phone was designed to be disassembled, and providing the chips were readily available (and forgetting that the cost of such a chip might be as much as the original phone) and assuming all goes well and you do not fry components or put a chip in wrong... yes, you can do it.

bBt you can apparently root your phone, change the software, delete the stuff you do not like, and do it for less effort than replacing chips, why bother with the chip replacement, just a little flash here and there.

Bob Maxey
 
This would have to be a dabbler slash fiddler slash hacker product because the general public will never want a build it yourself phone. Hell, the average person really does not know how to solder, much less about the dangers of ESD.

But, as with all technology, the market determines if it lives or becomes an also ran.

Bob Maxey

Following the links would've saved you the speculation.

The Neo1973 Freerunner is a product, offices in Taiwan, fabbed in China as memory serves.

Just as Linux was open software, the hardware offered an open license as well.

Killed by the same companies that swore to support it, the young, naive, but highly intelligent, founders never saw it coming.

In its heyday, it was shaping up to be THE Killer Device.

Your conclusions are based on an assumption that never reflected what happened.

The market didn't get what the market didn't deserve.

And the Android you're running is standing, just a bit, on Openmoko's shoulders.
 
Following the links would've saved you the speculation.

The Neo1973 Freerunner is a product, offices in Taiwan, fabbed in China as memory serves.

Just as Linux was open software, the hardware offered an open license as well.

Killed by the same companies that swore to support it, the young, naive, but highly intelligent, founders never saw it coming.

In its heyday, it was shaping up to be THE Killer Device.

Your conclusions are based on an assumption that never reflected what happened. The market didn't get what the market didn't deserve.

And the Android you're running is standing, just a bit, on Openmoko's shoulders.

Perhaps it will/would have some appeal to a small number of users, but it is not the killer device people want. Most do not want a kit of parts or a burning need to modify the hardware inside the unit. Or to end up with a broken device that wont work because of a poorly soldered connection, or lifted pad caused by too much heat, or cold solder joints and ESD damaged components.

And they likely wont order their cell phone from overseas suppliers. But, I might consider ordering something and having a look see. Thanks for the link and heads up.

I see it is not sold here in the U.S. of A. Do you know it it is FCC approved? If not, it is dead. I would be interested to know if a home built cell phone would ever be FCC or carrier approved. Or is it allready?

Bob Maxey
 
Perhaps it will/would have some appeal to a small number of users, but it is not the killer device people want. Most do not want a kit of parts or a burning need to modify the hardware inside the unit.

I didn't bother reading further.

This isn't some lame heathkit phone and your continued insistence that it is - is a complete product of your imagination.

It was a finished product. It was much like whatever phone you're carrying.

The license to build similar copies by any other maker - was open and free.

That's it, Bob, the whole enchilada.

It wasn't for a niche market - ALL of the major makers at the time encouraged these guys to push forward with the business - they received industry recognition.

Google was highly criticized for being one nail in their coffin when they announced Android.

Several handset makers went back on their stated intentions the day the shock hit that the founders were serious and actually got the first units fabbed.

It _was_ shaping up to be the killer device - and in its day, the prototypes were exactly that.

Freerunner02.gif


http://wiki.openmoko.org/wiki/Applications

http://video.google.de/videoplay?docid=-8343770443102960945#

As of now, with the Android onslaught, and no takers on the open hardware concept, the idea is all but dead.
 
I didn't bother reading further.

This isn't some lame heathkit phone and your continued insistence that it is - is a complete product of your imagination.

It was a finished product. It was much like whatever phone you're carrying.

The license to build similar copies by any other maker - was open and free.

That's it, Bob, the whole enchilada.

It wasn't for a niche market - ALL of the major makers at the time encouraged these guys to push forward with the business - they received industry recognition.

Google was highly criticized for being one nail in their coffin when they announced Android.

Several handset makers went back on their stated intentions the day the shock hit that the founders were serious and actually got the first units fabbed.

It _was_ shaping up to be the killer device - and in its day, the prototypes were exactly that.


As of now, with the Android onslaught, and no takers on the open hardware concept, the idea is all but dead.

You are right, and I stand corrected. What threw me was all the talk about the hardware being open source and the PCB was constructed so hardware hackers have, (to quote the web site) "A debug port with complete access to all the low-level hardware was added, along with interesting signals at easily solderable contact pads so hardware hackers can have fun." This suggested that the product was aimed at hackers and not the general public. A debug board was supplied; not to mention, displays, cases and the need to do lots of soldering.

Apparently, the only way to upgrade these devices is by replaceing the motherboard. Not a problem for developers that would likely want to modify the product. All in all, I simply assumed something and should have been a tad more clear.

So I was wrong to characterize it as a kit, but it is quite close and all current products are offered as parts or soon, as engineering samples. And yes, I know they offered a ready to go phone.

I never compared it to a Heathkit product, although I still use one of their signal generators and it works to this day.

The concept is a good one, I think.

Bob
 
It wasn't for a niche market - ALL of the major makers at the time encouraged these guys to push forward with the business - they received industry recognition.

Ok, the OpenMoko guys had super cool phones and I really wished they would have continued, in that direction. And yes, the phones came already put together, the end user didn't need to solider anything.

But, it was tailored for a niche market. The phones were designed for people who wanted the ability to customize everything and anything. Thats not your average smart phone user.
 
That's just untrue.

The initial phones being sold - with hardware access - was for developers. That's why you see so much that's customizable, and that's the final legacy.
 
<forehead slap>

OpenMoko is dead. They came out with the expectation of making the first - but by no means the only - open handset with an open OS.

The initial phone was always to be in two forms - the dev version and the regular version.

The target was Joe and Jane PhoneUser - not a niche market.

These were graduate students who ended their schoolwork with this as their thesis. They presented it publicly, and it was a shot heard around the world. Fearing they'd look stupid for not supporting the kiddies, several handset makers stood up within hours and days of their presentation and said they'd support open hardware and Linux.

Then the excuses came in.

Then the kids decided to believe the excuses - so they thought they'd help. Before anyone could blink, they moved to Taipei, opened offices, and got a deal going with - and this from memory - Foxconn, same guys making the iPhone, in China.

Knowing their strengths and limitations, they decided the best path to follow was Linus Torvalds' one, only with hardware - so the next thing you know, the dev phone was born.

But it was never the target market - not ever. Their vision from the beginning was quite clear: it was to end the tyranny of vendor lock-in for phone customers. That's something we all see complained about far and wide across our forums today.

With open hardware and an open operating system and open apps, you could take a simple backup of whatever you running and just put it on the next open phone of your choice, perhaps with different hardware features.

It was a nascent movement at open standards all the way around.

It especially included the profit analysis for the phone makers and projections as to how it would revolutionize smart phones.

The Android revolution is taking place using only half of the concept. With open hardware and firmware, locked bootloaders would have been unheard of.

And open hardware is NOT a new concept - it's simply unknown to many people, and even includes open firmware (open firmware is something found on PowerPC Macs, and a great many of the better unix workstations).
 
Back
Top Bottom