HTC Mogul Sprint ROM - GPS and REV. A New info!

[Yay 4 Juggs]

Originally Posted by livejazz

Funny, I actually have two different generations of those on my desk, right now.

HA HA he busted out the telxon!!!
but as another follow up to the follow up this is a slight hint that sprint effed up and is willing to kiss a little a

Dear XXXXXXXXXXX,

Thank you for the reply. I will be happy to assist you regarding the shipping of the free phone.

As promised to you I have sent the new LG LX 750 Music Phone free to you. the phone will be delivered at your mailing address within next 3 to 5 business days.

I hope this resolves the concern as per your satisfaction; however, if there is any more assistance required, please feel free to write back to us and we will be here for you.

Thank you for contacting Sprint. We appreciate your business, and look forward to providing you first class service in the future. Have a great day!

Sammy S.
Business E-Care
Sprint
"Where our customers come first!"

[livejazz]

Lame, but effective........

[Yay 4 Juggs]

very lame indeed...but atleast they admitted guilt.

[dishe]

Originally Posted by shaun0207

In my above post, I asked if a Sprint ROM and a Alltell ROM could be crossed. is that possible?

Sorta, the problem is what do you take from each ROM?
Meaning, if you extract the Bluetooth stack from the new ROM that fixes the quality issue, it might bring with it the bug in the power settings that keep it from coming out of standby when you press the power button... Or maybe the D-pad freezing issue.

The code is very complicated, and while we can mess around with modules, its sort of a gamble as far as predicting what will work vs. not. We didn't develop the rom so we don't know what purpose everything has.

Stuff like this is being tested, and believe me when we've got a solid and reliable solution, it'll be posted somewhere.

Originally Posted by TC1

While I agree with the ideas and intentions here, in reality this is not really practical. I'm speaking from experience, someone who has been an integrated circuit designer who use to design microchips for OEMS and manufacture OEM products.

I never said Sprint should be expected to support it. HTC should offer it to us, and Sprint can warn that this voids your warranty. I know its unlikely for many reasons, but it would really help the development community who ultimately ends up supporting HTC's phones better than even they can.

If anything, HTC might look like a hero to the few who are in the know, and sell more devices as the "open platform phone" to the cult followings. Sprint could create their own firmware and warn that if you tinker with custom ROMs, you are on your own. I think they're policy is sort of like this already, and we are already creating/flashing unsupported ROMs... so really the only difference is that HTC hasn't helped out the community and hasn't come out as the hero yet.

[shaun0207]

Originally Posted by dishe

Sorta, the problem is what do you take from each ROM?
Meaning, if you extract the Bluetooth stack from the new ROM that fixes the quality issue, it might bring with it the bug in the power settings that keep it from coming out of standby when you press the power button... Or maybe the D-pad freezing issue.

The code is very complicated, and while we can mess around with modules, its sort of a gamble as far as predicting what will work vs. not. We didn't develop the rom so we don't know what purpose everything has.

Stuff like this is being tested, and believe me when we've got a solid and reliable solution, it'll be posted somewhere.



.

Cool. thanks for the reply

[diomark]

It's BS that they posted such a crappy rom - but personally, I'm glad they did.. the custom rom folks have more to play with now as a result...

Personally, this rom is acting OK after I downgraded to the 1.40 radio - except my bluetooth keeps shutting off.. anyone find a fix for that one yet?
-mark

[TC1]

Originally Posted by dishe

If anything, HTC might look like a hero to the few who are in the know, and sell more devices as the "open platform phone" to the cult followings. Sprint could create their own firmware and warn that if you tinker with custom ROMs, you are on your own. I think they're policy is sort of like this already, and we are already creating/flashing unsupported ROMs... so really the only difference is that HTC hasn't helped out the community and hasn't come out as the hero yet.

I'm pretty much 100% sure that the carriers like Sprint have a contract with HTC that says that they can't provide resources like this to the general public, for the reasons I stated previously. So in this regard, HTC's hands are tied and this issue was decided when Sprint agreed to buy the Titan model from them.

As far as the device operating correctly, totally HTC's fault. I do believe they have seriously stretched their resources with all the different models they are trying to release. My bet right now is that either the Touch is going operate perfectly (because they have diverted resources to work on it from other projects) or it's going to be a worse nightmare than the Titan ever was.

[tannis]

WOW! The more I read this thread the more I think some people are just whinney babbies! ...... Don't swap your mogul for a touch the touch won't be Rev A right out of the box... if it is we'll just hack it for the mogul .... just like we do everything else

[Vinny]

Originally Posted by TC1

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.

Isn't Windows Mobile based on Windows CE? I know on CE you can get the platform builder and select which parts of the OS you include or modify. I would assume if WM is based on CE the same would apply. If so, the manufacturer or Sprint, whoever is responsible for the ROM, would have more say in the ROM than Microsoft.

[TC1]

Originally Posted by Vinny

Isn't Windows Mobile based on Windows CE? I know on CE you can get the platform builder and select which parts of the OS you include or modify. I would assume if WM is based on CE the same would apply. If so, the manufacturer or Sprint, whoever is responsible for the ROM, would have more say in the ROM than Microsoft.

That's a good question. I deal with Microsoft and their products professionally, I have a top-tier MSDN subscription which gives me access to all their platforms and development tools, but I've been too damned busy with other projects to poke around on WM stuff. I'm dying to find some time to load the mobile development tools up and see what I can break, lol.