Quantcast
Jump to content

PreCentral: Phoenix's Open webOS-on-Android project gets past the lock screen


News Reporter

Recommended Posts

Phoenix's Open webOS-on-Android project gets past the lock screen

While upstart hopes to someday put out their own hardware running our favored mobile operating system (we'll give you one guess as to what that operating system is), in the meantime they're focusing on a more-attainable project: , without having to make modifications to the Android device itself.

Where the is working on as a separate operating system, Phoenix wants to run Open webOS on top of Android, giving users the option to run both operating systems simultaneously instead of booting into one or the other. There are advantages to both approaches, so we're happy to have the potential for choices to be offered.

Several weeks ago we brought you the first look at what Phoneix was cooking up, showing off webOS opening as an app on Android. There was a problem, though: they couldn't get past the lockscreen, and attempting to do so crashed the OS/app. So at that point in mid-October, it was more of a proof-of-concept and work-in-progress than anything else. Fast-forward to today and the Phoenix team has made progress, as shown in the video after the break.

Not only can they now get past the lock screen, but webOS actually runs on their test Samsung Nexus S. It's not perfect - there's still a lot of work to be done - as the stuttering and sluggishness driven by the lack of working hardware acceleration shows, but it's progress. Phoenix says that the project is still in "pre-alpha" status; like the WebOS Ports port, it has to be launched via Terminal commands, though eventually Phoenix does plan to implement a launcher icon for the Android side of things. Phoenix has also borrowed some elements from the open source work of the WebOS Ports team, including .

Phoenix right now is entirely volunteer-driven, and as always they're looking for people willing to contribute their skills. Specifically, they're in need of people experienced with working on the Linux Kernel and operating system (), Android itself, and the GNU toolchain. If you're so inclined, go ahead and hit up the source link below.

mf.gif


a2t.img0VR1GosPZZU

link hidden, please login to view
Link to comment
Share on other sites

  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Topics

    • By Alfvenwave
      Hi, I'm curious if anyone else is seeing this annoying new behaviour.
      I have my SKY Q box on HDMI1 and have become accustomed to switching back from Netflix (or any other app for that matter) by having HDMI1 assigned to button "1" using the Quick Access feature.  In the last week though, this feature has stopped working properly. If I am in Netflix and I press the "1" button, nothing happens (as expected). If instead I hold down the "1" button to switch to SKY I get a pop up that says this: "Do you want to add Netflix to [Quick Access 1]?".   If I then hold down the "0" button, the 3x3 grid "EDIT QUICK ACCESS" pop-up appears and I can clearly see my SKY Q/HDMI 1 in the top left grid position (button "1")!!!
      If I then switch via the Home button to HDMI1 and remove HDMI1 from Quick Access (via the  EDIT QUICK ACCESS pop up), I can then re-add it by holding down 1 or from within the pop-up. Now, if I go into Netflix and then hold down 1, my TV does (correctly) switch to HDMI1. Hurrah! If however I turn my TV off and back on, then go to Netflix, then hold down "1", I am back to square one with the question "Do you want to add Netwflix to [Quick Access 1]?"......Grrrr!!!
      I have tried switching the TV off at the wall, leaving for 10 seconds and repowering, which doesn't fix the problem (I don't believe WebOS reboots when you do this). LG appear to have made it a practical impossibility to reboot WebOS via anything other than a factory reset which I don't really want to do as it'll take me too long to get all my settings back to where I have them now. Some blogs suggest that the "User Licence agreement" setting can be changed which forces a reset from within the General tab but I don't see this on my TV (guessing that WebOS interface has changed).
      Anyone have any ideas? 
      Rob.
       
    • By Mohannad Hanafi
      I installed webOS TV Emulator v6.0.0 and when I run it, it shows a black screen like this
      It's running on Oracle VM VirtualBox.

    • By yenn22
      Hi, since I think yesterday I have an issue with HBO GO - it just shows unsupported device and that is it. According to their website, WebOS 3.5+ should be supported, I have LG uh6107 and in menu it shows SW version  5.60.15, so I think it should be ok.. does anybody have the same issue?
    • By Anurag Rathi
      When I am trying to play premium content on hotstar, it is showing me the playback error. Please resolve this. In other devices it is working perfectly. I have raised this to hotstar they asked me to raise it to TV manufacturer. Attach is the screenshot of the issue.

    • By DRAEGNAROK
      I’d love to stream the upcoming F1 season directly from my LG OLED TV without depending on other devices to source it. When can we expect this app to be featured by LG? Thanks!

×
×
  • Create New...