Results 1 to 14 of 14
Like Tree9Likes
  • 1 Post By bearda
  • 2 Post By Preemptive
  • 4 Post By eblade
  • 2 Post By eblade
  1. alonhzn's Avatar
    Posts
    124 Posts
    Global Posts
    130 Global Posts
       #1  
    We all know that because webOS is not designed for the specific hardware of an existing phone, it can't just be installed without porting.
    My question is if webOS is complete in the sense that there is a hypothetical device that webOS can run on? in other words, if I could build a phone from any hardware parts i wanted, could i make a phone that runs webOS?
  2. #2  
    Yes.

    But trying to future-proof Open webOS, HP chose to use the standard Linux kernel, so the type of mobile hardware that can run OWO straight up, without modification isn't here yet. It will ship with the Android version codenamed "Key Lime Pie", and you'll still have the usual difficulties with the incompatible graphics driver models.

    If we were to rewrite the compositor to use the Android-style drivers, then this issue will be solved once and for all, with hardware-accelerated graphics being available on every device..
  3. #3  
    Technically, yes. Open webOS is complete in the sense that Android Open Source Project is complete. It is complete, as in it is functional.

    Realistically, no.There's A LOT that is missing. There are no Synergy connections other than IMAP email. There's no phone app, no camera app. no music app. etc. As we've seen with the Galaxy Nexus port job, there's a lot of tweaking that has to be done just to make it look right, let alone everything that has to be done to make the radios work, access the graphics chip, accelerometer, et al.

    So yes, while you can take Open webOS and throw it onto a device that supports its open source drivers, don't expect it to be anything approaching a good experience without a mountain of work first.
    "'Form follows function' that has been misunderstood. Form and function should be one, joined in a spiritual union."
    Frank Lloyd Wright
  4. #4  
    Thanks Derek.

    I figured everyone knew that already, so i focused in on the hardware, kernel and driver situation.

    The user-centric stuff will continue to stagnate until the usability situation is sorted out... because to make sure a mobile device performs well, the developer has to use it daily (that's how Apple's baseband engineer, Gray Powell lost a prototype iPhone 4 at the bar)... and no one can really stand a device with no hardware-accelerated video. Once that gets taken care of, working on other components will become more bearable.
  5. alonhzn's Avatar
    Posts
    124 Posts
    Global Posts
    130 Global Posts
       #5  
    The bare minimum is being able to make phone calls.
  6. bearda's Avatar
    Posts
    68 Posts
    Global Posts
    301 Global Posts
    #6  
    Quote Originally Posted by alonhzn View Post
    The bare minimum is being able to make phone calls.
    Then no, it isn't.
    dignitary likes this.
  7. #7  
    When I get time, I'll trawl the Ports site to see what's happening, but a few quick questions here:

    Does the Android OSP come without a dialer and the other stuff? I assumed there was 'stock' that would work on the Nexus spec and then OEMs customise it for their H/W & UX tweaks.

    If OwOS is so incomplete, is there any guess at the time scale (and in fact possibility) for completion? Months? Years? I ask because if HP don't fix the app catalogue, then legacy is basically circling the drain and users will likely go with it.

    I mean no offense to the developers who are working for free in their spare time & hope they are making good progress, but the parade is already passing by and if the project is ever usable on the Galaxy Nexus, it may already be too late.
    Remy X and Buddy1969 like this.
  8. #8  
    I've heard people say on #webos-ports that the telephony stack is actually functioning, and can be used from command line, which basically means that someone needs to wire it up to the places it needs to be wired to, and then a phone app either written or adapted.
    Author:
    Remove Messaging Beeps patch for webOS 3.0.5, Left/Right bezel gestures in LunaCE,
    Whazaa! Messenger and node-wa, SynerGV 1 and 2 - Google Voice integration, XO - Subsonic Commander media streamer, AB:S Launcher
    (1:39:33 PM) halfhalo: Android multitasking is like sticking your fingers into a blender
    GO OPEN WEBOS!
    People asked me for a donate link for my non-catalog work, so here you are:
    Remy X, Rnp, Preemptive and 1 others like this.
  9. #9  
    Thanks Eric

    It sounds like the feature only needs about an hour's work then...
  10. #10  
    THAT I don't know. If it -does- work from the command line, I could make some horrifically ugly and very temporary hack to put together something that would "function". Basically rob the dialpad out of SynerGV and attach it to the command line whatever.

    As far as actually wiring it to everywhere it -should- be wired inside webOS, I don't know if those parts are even included currently, and I know the official phone app isn't currently. (also the official phone app for 3.0.5 didn't directly make phone calls, however, it may be the exact same as the phone app that was in 2.2.4, so it might just be the fact that TouchPads didn't have phone transmitters that prevented it from trying to make actual phone calls)
    Author:
    Remove Messaging Beeps patch for webOS 3.0.5, Left/Right bezel gestures in LunaCE,
    Whazaa! Messenger and node-wa, SynerGV 1 and 2 - Google Voice integration, XO - Subsonic Commander media streamer, AB:S Launcher
    (1:39:33 PM) halfhalo: Android multitasking is like sticking your fingers into a blender
    GO OPEN WEBOS!
    People asked me for a donate link for my non-catalog work, so here you are:
    Remy X and pgarcia like this.
  11. #11  
    Quote Originally Posted by eblade View Post
    ...
    As far as actually wiring it to everywhere it -should- be wired inside webOS, I don't know if those parts are even included currently, and I know the official phone app isn't currently....
    So there is always the possibility to set the device on fire and use a blanket to communicaty via smoke signs ...
    That's probably what the devs at HP had in mind anyway.

    [/irony]
    War doesn't prove who's right, only who's left...
  12. #12  
    Does anyone have any idea how much the licensing fees for Exchange ActiveSync would be to be paid to Microsoft? I assume this is a per device fee that would need to be paid?
  13. bearda's Avatar
    Posts
    68 Posts
    Global Posts
    301 Global Posts
    #13  
    Quote Originally Posted by Herrie View Post
    Does anyone have any idea how much the licensing fees for Exchange ActiveSync would be to be paid to Microsoft? I assume this is a per device fee that would need to be paid?
    Last I heard baseline was $100K for the first year, and per unit royalties from there after.
  14. #14  
    Hmm that's steep :-(

    -- Sent from my TouchPad using Communities
    HP Veer (daily driver), HP Pre 3, HP Touchpad Proper 4G/LTE (Sierra MC7710), HP Touchpad 32GB WiFi, Palm Pre 2

Similar Threads

  1. What can we make of this open-embedded core business for Open webOS?
    By dr3wster in forum Open webOS General Discussion
    Replies: 1
    Last Post: 09/02/2012, 11:11 AM
  2. Engadget: Open Source, Open Issues for webOS
    By rmeigs in forum HP TouchPad
    Replies: 0
    Last Post: 12/22/2011, 04:51 PM
  3. complete noob to webOS
    By mel_vin in forum HP TouchPad
    Replies: 22
    Last Post: 07/06/2011, 09:36 AM
  4. Apps/Features needed for webOS to be complete
    By stockh in forum webOS Discussion Lounge
    Replies: 9
    Last Post: 10/17/2010, 09:15 PM
  5. Complete WebOS Back-up via Windows
    By BruceBradford in forum General News & Discussion
    Replies: 2
    Last Post: 08/15/2010, 08:46 PM

Posting Permissions