|
|
||||
The touch is a different line than the Mogul and you can't really consider it an upgrade or downgrade from the Mogul as its intended for a different market.
The cpu and chipset are the same as the mogul and this makes some of the hardware specific drivers compatible with the mogul's hardware (i.e. bluetooth drivers). The Touch has twice the RAM as the Mogul as well. However, it also lacks the wi-fi, hardware keyboard and flash/flashlight that the Mogul has.
__________________
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 |
|
||||
Although I agree that the Touch is a different line from the Mogul, the Touch is considered the 6900 as the launchpad site on the Touch's PIE shows it this way and it is identified as such on Sprint's system.
When I called to activate the rep asked me if my new phone was a 6900, not a Touch, when I have him the ESN.
__________________
Samsung Epic 4G - LegendaryROM / Samurai kernel
ViewSonic gTablet - Flashback Honeycomb Alpha 10.1 --- Don't forget to Search first! |
|
||||
Why would it be impossible for one to physically upgrade the RAM inside of their Mogul so that it is equal to the RAM in the Touch?
Is RAM in WM devices that hardwired to the phone that it's impossible to open the phone up and put in extra RAM? The physical RAM amount in the Touch can't be that much bigger then the physical RAM amount inside of the Mogul. |
|
||||
Quote:
![]()
__________________
HTC EVO 4G - Fresh 0.3
|
|
||||
I just picture the RAM in the Touch as being equal or close to equal to the same size and shape as what's inside of the Mogul. IF we can find someone skilled and trained enough to do "swap outs" of RAM into Moguls, then that would be awesome. I call it interesting to look and see.
|
|
||||
noo
well sprint better come out with a look alike mogul upgrade in less than a year cuz i really dont like the touch since it doesnt have a hardware keyboard and no wifi....why couldnt they cll it the "TOUCH"........now they ruined the name for the successor of the mogul,.....and i dont consider the touch as the successor of the mogul
|
|
||||
Quote:
Take for instance the fact that 64MB of RAM doesn't require an address bus larger than 24 bits, assuming that you have a 4-word-addressable memory. Addressing 128MB of RAM consequently requires 25 bits in our 4-word scheme. Why would they add the extra PCB traces to accommodate, say, the full 32-bit address bus, if the memory installed will never be more than what the factory intended? So add either 24 or 25 traces for the address bus, and you've saved realestate on a small embedded device platform. The above doesn't imply that the address bus doesn't have the full 32 bits available, but it is nonetheless an assumption, and may be problematic. The second assumption is that memory timing and latency is the same. It may be, and if it is standard SDRAM, a slower timing will work just fine on faster, newer memory. But what if the power requirements are different? It's well-known that more RAM means a bigger drain. This is because of CMOS leakage current within the device. The more gates/transistors you have, the more current leakage you are going to have. (SDRAM uses capacitive memory, but it still must be switched. Also, given that it is capacitive memory, it takes more power to recharge the RAM cells than if you had fewer of them, as in 128MB vs 64MB.) A way around this is to change your operating device characteristics. Build a lower-voltage device circuit, and change your device characteristics (transistor size, gate width, etc.) so that your leakage isn't as bad. If the power supply to the memory is different, then there is essentially no chance that you will see a RAM upgrade, especially not from the Touch. These are just some points - simply moving a chip because the dimensions match says nothing about their interoperability. It'd be NICE, but keep in mind that embedded devices aren't as standardized as PC memory, where the end-user is actually responsible for their own memory upgrades (usually anyway.) Therefore, it makes it a lot more difficult, in the long run, to make embedded device parts interchangeable, and leaves us SOL because the manufacturer chose one part over another. Last edited by APOLAUF; 11-11-2007 at 03:25 PM. |
|
||||
Quote:
|
![]() |
|
|
|