Results 1 to 6 of 6
Like Tree3Likes
  • 3 Post By somline
  1.    #1  
    So what are the hardware related issues we would face with getting a webOS port working on another phone? I assume the device would have to have a similar chipset, so that means that it would likely have to share the internals of the pre 2 or the touchpad. That limits us to the following

    TI OMAP3630-1000 devices (webOS 2.x only):
    Nokia N9
    Nokia N950
    Motorola Milestone 2 (locked bootloader, but has been cracked iirc)
    Motorola Cliq 2 (locked bootloader)
    Motorola Defy+ (locked bootloader)
    Droid X (locked bootloader)
    Droid 2 (locked bootloader)
    LG Optimus Black
    LG Optimus bright L-07C
    Samsung I9003 Galaxy S(C)L
    LG-LU3000 Optimus Mach

    S3 APQ8060 (no radios and must run webOS 3.x):
    Galaxy SII devices (excluding the Galaxy Nexus)
    HTC Vivid
    LG Nitro HD

    So, for any of the moto devices, a way around the bootloader would have to be found.

    Also, a way of mapping gestures to physical buttons would have to be established or setting aside real estate on the screen to act as a gesture area.

    Anything else?
    Last edited by OldSkoolVWLover; 12/20/2011 at 04:47 PM. Reason: fixed title typo
  2. #2  
    I assume you aren't a developer or have knowledge about device drivers.
    There is a lot more than the processor. You may have followed the Android port to the TP and the problems they had with the digitizer, wifi, A6 and so on.
    And they had the source code of android.
    Without the source code of webOS it's (almost) impossible to port it to different devices.
    dignitary, Rnp and xandros9 like this.
  3. #3  
    someline is right, there is a ton more than just chipsets. Eventually developers will port WebOS to completely different chipsets so that isn't the main issue. Ports take time because each phone has different features that need to be enabled and it means the porter (developer) has to write and properly implement drivers to the port. This means volume buttons, functioning gesture areas whether its button or touch needs to be coded for, cameras both front and back, graphics acceleration, wifi, radio, even the touchscreen has to be accounted for.
  4. #4  
    Don't forget the Motorola Droid Pro and Pro+ and Admiral...they have non-slider full keyboards. That one feature would make JustType so much more useful.
  5. #5  
    Wouldn't it be easy since all you would have to do is look at the open source Android code that already enables those functions and just convert that to webOS? Aren't they both Linux based already?
  6. #6  
    One thing of note is that the Pre 3 runs on a Snapdragon S2, so that adds a few extra devices into the mix....


Posting Permissions