|
||||
Quote:
![]()
__________________
Treo 600 -> Treo 650 ->Treo 700p -> Treo 700wx -> Mogul -> Touch Pro -> Touch Pro 2 -> HTC Evo
- [Guide] Get Root access & NAND Unlock your Evo (Full Root) - My Current AppBrain List |
|
||||
Quote:
Ohh ok. Are you sure though? Sometimes if you dont send the defective phone back to them, they charge your account for it. |
|
||||
I dont mean to disagree with you, but that message doesnt read like that to me. But if they do it , great for you.
I think they need to do something liek for all Mogul customers. In my above post, I asked if a Sprint ROM and a Alltell ROM could be crossed. is that possible? |
|
||||
Quote:
__________________
........ and the moral of the story is: "you can't have a drink on the house"
|
|
||||
Quote:
![]() Quote:
Any ideas? Also, even though they are offering you a free phone until the Mogul is fixed, I would tell them that you shouldn't have to step down a device until they fix these issues.
__________________
Samsung Epic 4G - LegendaryROM / Samurai kernel
ViewSonic gTablet - Flashback Honeycomb Alpha 10.1 --- Don't forget to Search first! |
|
||||
Quote:
I agree. You shouldnt have to step down a device. |
|
||||
Quote:
In the first example you listed above, Target gets to customize the product and distribute it to their customers, ie, internal Target business units. When something goes wrong, who do the business units call? That's right, Target IT, not the manufacturer (like an HTC). The manufacturer has no idea what Target did to these devices and it's unfair to expect them to magically troubleshoot them (unless a secondary support contract was signed). So I ask the question, how is the statement "Now, how amazing would it be if HTC just handed the SDK over to us and said "here, we saved you the trouble. Make the phone work how you want it to"" practical? The phone in this case does not operate in a vacuum, it operates on Sprint's network and is sold by Sprint. Imagine all the folks that think they know what they are doing get a hold of the SDK and start modifying the phone on their own. Sure, Sprint might have something in their warranty that says "We are not responsible for 3rd party software, user modification, blah, blah" but do you really think that will stop all the folks who brick their phones from calling Sprint anyway? Their logic will be "Hey... if we weren't suppose to play around inside the phone, why did they release this SDK to us?" Sprint will get bombarded with calls, making their crappy customer support even crappier. It will be an unplanned for financial hit to Sprint's overhead costs. I think the real solution to what you are getting at is that the CDMA carriers operate the same business/technology model as the GSM carriers: Here's a SIM card, bring your own phone to the party. That way there can be everyday folks who just want a phone that can buy it from the carriers, then there will the power users that can buy the phone directly from the manufacturer and pop in a SIM card to get the carrier of their choice network. Since you bought the phone on your own, the carrier doesn't have to stand behind it, they just have to make sure their network complies with certain standards for interoperability. And to diverge a little here, the problems we are seeing with the Mogul are not really the fault of Sprint. Yes, Sprint is ultimately responsible since they sold you the product, that's a fact. But here is how the PDA phones are developed: 1. Microsoft makes an OEM version of their operating system available to the manufactures/OEMs, ie, HTC, Samsung, and others. 2. Various integrated circuit manufactures design cips that will support both operating system and the cell phone functions needed. 3. Manufacturers like HTC design a product using various sources of info, the two predominant ones being "reference designs" provided by Microsoft and the chip makers (Qualcomm, etc). It is up to the manufacturer to make the hardware and software work together, ie, specialized drivers. Who develops these drivers is variable, sometimes the chip makers make baseline ones available to be tweaked, sometimes the chip makers just make the hardware API spec sheet available and it's up to the manufacturer to write their own drivers. 4. The manufacturer will attempt to 'add value' by incorporating features in software, like the TouchFlo interface (developed in house by HTC) or incorporating a third-party innovations (like Samsung did with the Picsel browser). The idea here is to make a product that many of the carriers will want to carry in their product line. 5. The carrier will submit the OEM version of the product to the FCC for use acceptance on the U.S. airwaves. 6. The various carriers will buy the OEM version from the Manufacturer and then say "Ok, this what we want you to do to make it 'our' version." At a minimum this includes almost always the outer cosmetics, ie, the case, its colors and materials, silk screened logos, buttons, etc. 7. The final thing that is done is that the the carriers will develop some minor crapware of their own to generate additional revenue. One needs to keep in mind that this crapware just sits on top of the OS like any other 3rd party application, they are not redesigning the code of the OS or the drivers. So as can be seen from the above process, a carrier like Sprint or VzW are only involved in two steps, and only the last step has any remote possibility of screwing up the functionality of the finished product (except for the wonderful folks at VzW who supposedly screwed up step #6 with their initial button design). Things like BT not working are more than likely the screw up of HTC, the chip maker (Qualcomm?) or Microsoft. Sprint simply does NOT do deep firmware development on these devices, it was decided years ago by the carriers to shift these types of costs onto the OEMs. I'm not trying to make excuses for Sprint, they do indeed deserve the wrath of the consumer, I'm just trying to put things into perspective here. |
![]() |
|
|
|