|
 Originally Posted by EvilKell
Wasn't there a lot of problem creation when moving from webOS 1.4.x to webOS 2.x due to the Palm profile database structure or something like that? I wonder if that would play into the issue of the Pre and TouchPad?
I am thinking devices running software prior to 2.x won't be able to share profiles. I also am thinking if the app cat doesn't get fixed, devices prior to Pre 2 may not be able to share profiles (even if they have been dr.d to 2.x).
To clarify this thought before anyone jumps on my ****... I am looking at how everything else is evolving around the app catalog and 2.x devices. Doesn't seam like this is going to be backwards compatible very well. Not saying it can't be done, just thinking HP doesn't want to waste resources on compatibility and stability of devices that are around 2 years old. (like it or not I am just being realistic)
 Originally Posted by fxspec06
That was because a lot of people from this forum were 'unsupportedly' meta-doctoring to 2.1. Everyone who made the switch officially had no problems.
From what I remember this is incorrect information. Once a profile has been upgraded to 2.x, it cannot be properly used on a 1.x device. Even if the profile went to 2.x on an authorized 2.x device (Pre 2, Veer, some Pre+'s). This is because when being used on 2.x their are changes made to the profile.
Just saying I don't recall it being specific to meta-doctoring. Just that meta-dr 2.x devices might want to go back to 1.x. Where Pre 2/Veer wouldn't be dr to 1.x. I am thinking you would have the same problem say using your 1.x profile on a Pre 2/Veer, then going back to your 1.x device.
This is all from memory, not that I have done it. I just remember it being a function of the new way Palm Profiles are going to function.
|
|
|