Quantcast
Jump to content

  • Join Today, It's Simple and FREE!

    Register now to gain access to our webOS user support forum. Once registered and logged in, you will be able to post a user to user support request topic to this site or reply to existing topics posted by other users. You can also take part in our other webOS user forums. You'll be able to customize your profile, receive reputation points, while also communicating with other members via your own private inbox, plus much more!

Sign in to follow this  
NewsDummy

PreCentral: CyanogenMod 10 for the TouchPad almost ready for prime time

Recommended Posts

CM10 for the TouchPad almost ready for prime time

Back in August, TouchPad hacking mastermind James Sullins released a really early build of CyanogenMod10 for those of us daring enough to try something that is far from stable in the Android-on-your-TouchPad world. At the time this early ROM worked but was missing several key elements like sound and hardware acceleration. Despite missing some fairly important things for the typical daily driver, James' early build showed a bunch of promise and oozed the buttery smoothness that is a staple point of Android 4.1 (aka Jellybean). However, after the initial release James disappeared, leaving us all craving for some more Jelly Bean action. After several months we were starting to think the project was dead. Then, out of seemingly nowhere, a new build of CM10 hit the interwebs and to our surprise it's amazingly stable, despite being carrying an experimental pre-alpha build label.

So what has changed? First and foremost, CM10 now has sound and hardware acceleration, so Netflix and YouTube lovers will be happy with their video framerates and, well, having audio. This build also has working microphone functionality, which has been a sore spot for CyangenMod 9 TouchPad users due to the proprietary drivers needed for our beloved tablets. During our testing we have found that mic functionality is a bit finnicky, especially when trying to use Google Now. It's still pre-alpha, so take that performance with a grain of salt. Outside of that, almost every app we tried from simple Twitter apps to graphically-intensive games all worked without a hitch.

With all this goodness in tow you are probably wondering why this hasn't been released as an alpha or an official nightly. Well, that's because there are several kinks that still need to be ironed out. For example, many people from the various forums following this build have experienced several different battery and charging issues. During our testing of James' newest build from November 8 we experienced fantastic battery life in comparison to what we've experienced with CM9. That said, our TouchPad on this CM10 alpha wouldn't take a charge without turning on USB debugging in Android's developer options. Don't ask us why this managed to fix the issue, but it did. In addition to battery and charging issues, users may also experience the occasional force close of an app and no camera support (no surprise on that one, and not a great loss considering the quality of the TouchPad's lone front-facing camera).

Outside of the above-listed issues we have found this build of CM10 to be pretty darn stable. So much so that we probably won't be moving back to CM9 anytime soon for our Android needs. But that's only because we've already got it installed - like all things experimental (see the Open webOS porting process onto the Samsung Galaxy Nexus smartphone), we aren't yet ready to suggest you dive in with CM10 as a daily driver operating system. But if you are the adventerous type, just hit up the source link below for more info. As soon as something more stable is released, be prepared for full walkthrough on how to get your TouchPad up to date with CM10. If you have yet to take the plunge and dual boot your TouchPad with webOS and Android 4.0, be sure to check our our great how-to on installing CyanogenMod9 on your device.

mf.gif
emailthis2.gif bookmark.gif


a2.imga2t.imggZfNe8Txdq4

View the full article

Share this post


Link to post
Share on other sites


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Similar Forum Topics

    • LG INTRODUCES WORLD’S FIRST 8K OLED TV

      First To Mass Produce Large Screen OLED TVs, LG Poised to Lead Market in Advanced Premium TV Technologies BERLIN, Aug. 29, 2018 — Already a leader in advancing TV innovation with its OLED TVs, LG Electronics (LG) is introducing the world’s first 8K (7680 x 4320) OLED TV. Previewed at IFA 2018, the 88-inch class 8K LG OLED TV features over 33 million self-emitting pixels to produce the unmatched contrast ratio and true blacks that define OLED TV’s iconic picture quality. With OLED TV shipments in the market expected to double in 2018 and reach over nine million units by 2022, LG will continue to increase the OLED share in its premium TV portfolio and drive large scale consumer adoption of OLED TVs. While the 8K TV market is still in its infancy, it is expected to grow to more than 5 million units by 2022, and LG is committed to leading the ultra-premium market with its 8K OLED TV technology. Despite advancements in LCD field, OLED has been often referred to as the “nextgeneration display technology” because it emits its own light, eliminating the need for any kind of backlighting. This allows for state-of-art TVs which redefine both the picture quality and the product design. Not only was LG able to pioneer such technologies, but it was also able to successfully market them. “LG’s first 8K OLED TV is the pinnacle of technological achievement and the next evolutionary step in display technology,” said Brian Kwon, president of LG Home Entertainment Company. “4K OLED played a major role in reshaping TV industry and LG is confident that 8K OLED will do the same.” LG introduced the 88" 8k OLED TV at CES 2018  

      By Alex, in LG webOS Smart TV Discussion

        
      • 3 replies
      • 688 views
    • [pivotCE]LuneOS November Stable Release: Doppio

      The very long wait is over #LuneOS and #webOS fans! We’re finally back with a new release called “Doppio” which we believe will be a milestone in terms of developments and the way forward! So you’re wondering what we’ve been up to for the past year? Well, actually a whole lot to be honest! We have upgraded the bluetooth stack from BlueZ4 to BlueZ5 which required quite some work to the kernels. This has been successfully completed for the Nexus 4 (Mako) and Nexus 5 (Hammerhead); unfortunately to date we haven’t been able to get this to work on the Touchpad (4G) (Tenderloin). We have been working closely together with the Halium project and have made further integrations between LuneOS and Halium reducing duplication between the projects and using a single source where possible. This all to be more easily integrated, and to facilitate ports to newer devices. We have upstreamed our kernel patches (mainly to fix GCC 5/6/7/8 compatibility) to Halium so we can use a shared kernel for our targets. Talking about new devices we’ve been working on: Since Google dropped the (budget) Nexus line and launched the (premium) Pixel line, we’ve been looking for other targets that are easily available, budget friendly and have good community support. We quickly ended up with Xiaomi which makes phones with decent specs, unlockable bootloader (the process is a bit tedious, but it’s do-able) and the phones give very good value for money. This has resulted in us independently working on 3 different Xiaomi devices being the RedMi Note 4x (Mido), RedMi 5 (Rosy) and Mi A1 (Tissot).  These are all Aarch64 devices using the Snapdragon 625 chipset. We didn’t have any Aarch64 devices before and also they are based upon Halium 7.1 (Android 7.1) while all our previous targets were based upon Halium 5.1 (Android 5.1), so this brought a whole bunch of new challenges. There are still a few rough edges, but audio, sensors, wifi and bluetooth are now working. There was also quite some porting work done for some of the other Halium supported targets such as the OnePlus X (onyx), Google/Huawei Nexus 6P (angler) and Motorola G4 (athene). These are currently in various stages of development, whereby OnePlus X is the most mature. The Xiaomi Mi A1 is a strategic device for us which we chose in cooperation with LG to work on to get LuneOS working and also as a target for LG’s webOS OSE (Open Source Edition). LG’s release of webOS OSE came as a surprise to us, however it has great potential. Though the initial release of webOS OSE was very limited and therefore limited use case for people not being very familiar with webOS, it does offer a lot of potential for us. webOS OSE is basically 5 years of development of the core webOS bits since Open webOS was released. It has been deployed in millions of LG TV’s since and offers great improvements in terms of reliability and functionality. The big downside however is that there’s no record of the changes between Open webOS and webOS OSE, so this is making the migration a bit more challenging. Early June the LuneOS team met with LG in Paris to discuss collaboration between our teams. As a result of this we have chosen the Xiaomi A1 as a device to port LuneOS to. This is now at a level similar to our other targets. After this release we will therefore focus on migrating our Open webOS components to the updated components provided by webOS OSE. This will bring quite some challenges and hurdles along the way, however we’re positive that we can complete this migration and it will bring a lot of improvements in terms of code quality, stability, functionality and reducing the need for maintaining a lot of these components ourselves since we can share a common codebase with LG’s webOS OSE going forward. LG has a very clear vision in mind for webOS. Since the initial release in March, a roadmap has been published and LG has pushed out 4 releases since the original release of webOS OSE. The following items on our to-do list will be where we focus next: Migration of Open webOS components to the newer webOS OSE components. Make the VirtualBox image work with a newer MESA. Migrate to Yocto Sumo/Thud release. Messaging improvements. Camera improvements. Fix known issues on the various targets. Bring back official support for Touchpad 4G (current build works on Touchpad 4G but only WiFi). Known issues: Node-SQLite3 is currently not working. Components using Node-SQLite3 have switched to an alternative storage method for now. Focus bug on input fields. You can work around this by hiding the virtual keyboard and pressing the input again. Random issue with virtual keyboard not showing on Aarch64 devices. Changelog Applications: Settings: Add QML variant, enable manual time and date in Setings. org.webosports.cdav: Add CLEANBROKEN User Interface: luna-{sysmgr,sysmgr-common,appmanager,next}, mediaindexer: fix build with Qt 5.11. luna-{webappmanager,qml-launcher} org.webosports.app.{browser,firstuse}: fix build with Qt 5.11. luna-next-cardshell: add runtime dependency on qtmultimedia-qmlplugins, luneos-components. luneos-components: drop build time dependency on qtwebengine, switch to Mer’s bluezqt System Level: luna-next: Add config for onyx, Add QT_OPENGL_NO_BGRA and remove QT_ENABLE_GLYPH_CACHE_WORKAROUND android-gadget-setup: fix functionfs test android-tools: fix compatibility with adb 5.1.1 android-tools-conf: Fix the machine check, Don’t patch script for tenderloin base-files: provide a common fstab for all LuneOS devices bluez: switch from bluez4 to bluez5 bluez5: Fix patch so it will work for RaspberryPi3, make firmware search case insensitive connman: Add connman-tools, connman-tests and connman-wait-online, Update to 1.35 distro: luneos: switch release name to Doppio environment.conf: Add QT_ENABLE_GLYPH_CACHE_WORKAROUND=1 fingerterm: Update to upstream and drop patch, use LiberationMono font funyahoo-plusplus: Bump SRCREV https-everywhere: Bump SRCREV hunspell-dictionaries: Update to latest version imaccountvalidator, imlibpurpleservice: Drop unsupported protocols initramfs-boot-android: add A/B partition support, boot into built-in recovery when no skip_initramfs, get Halium’s init script from GitHub, improve panic scenario in init.sh, use /userdata instead of /android/userdata, Various fixes to init.sh kf5bluezqt-mer: fix package content with empty QT_DIR_NAME libconnman-qt5: fix initial value of “connected” property libhybris, qtbase: don’t use += together with _append libhybris: Bump SRCREV, Set –enable-arch=arm64 for aarch64, Drop –with-default-hybris-ld-library-path and bump SRCREV libpbnjson: use Unix Makefils OECMAKE_GENERATOR lsb: fix luneos-version content luna-(web)appmanager: use /etc/luna-next/qtwebengine.conf luna-init, luna-sysmgr: Bump SRCREV and adjust file installs luna-init: Fix incorrect {, Install CustomerCareNumber.txt and cust-preferences.txt luna-prefs-data: Bump PV to be in sync with luna-prefs luna-sysmgr: Cleanup recipe luna-sysmgr-conf, nyx-modules: fix rosy values, Add initial files for athene and onyx target, Cleanup recipe and fixup defaultPreferences-platform.txt luna-universalsearchmgr: inherit webos_systemd luna-webappmanager: bump SRCREV luneos.inc, connman: Build & deploy VPN plugins luneos: inherit remove-libtool luneos: update SANITY_TESTED_DISTROS luneos-dev-image: tell Halium to mount rootfs rw luneos-emulator-appliance: update a bit luneos-features, connman: Add support for NFC using neard luneui-example-image: add few more packages, add more packages for testing, add vboxguestdrivers, v86d, add very small (fast to build) test image maliit-framework-qt5: set XDG_RUNTIME_DIR in conf file meta*: enable gbm meta-webos-ports: Add configuration files for Tissot, Update classes with info from webOS OSE mido, tissot: Fix path for CHARGER_AC_SYSFS_PATH mido: Initial configuration files mobile-broadband-provider-info: Bump SRCREV mojomail: bump SRCREV to fix build with boost-1.67.0, Switch back to webOS-ports/master branch nemo-qml-plugin-dbus: Update to latest version from upstream, fix package content with empty QT_DIR_NAME node-sqlite3: Bump version nyx-conf: do not let keys module watch over the touchpanel nyx-modules: Fix devices names in cmake files ofono: Update to latest version from upstream and enable Python 3 tests onyx: Enable power button packagegroup-luneos-development: include QML settings app packagegroup-luneos-extended: add android-kernel-bootimg, Add qtconnectivity, Add WIP targets and more documentation, Build bluez5 for all targets, include libpci for qemux86, move android-kernel-bootimg phonesim: Fix build with empty QT_DIR_NAME, refresh patches with devtool, update to latest revision from git pidgin-sipe: backport a patch to fix build with gcc8 pulseaudio-distro-conf: Add support for Xiaomi A1 (tissot), Add webos-system.pa for mido target pulseaudio-modules-droid: bump to 10.0.73, refresh patches with devtool, remove tenderloin CFLAGS purple-skypeweb: Bump SRCREV python-tz-native: Update to 2017.2, Fix typo in SRC_URI qt5: upgrade to 5.11, upgrade to 5.11.1 qt5-qpa-hwcomposer-plugin: fix package content with empty QT_DIR_NAME, hwcomposer_backend.h: Fix cast from ‘void*’ to ‘unsigned int’, remove tenderloin CFLAGS qtbase: Add patch to fix quirks with newer Adreno GPU’s, refresh patches, remove TLS patch on Halium 7.1 targets, temporary fix for SIGBUS crash on Android devices qtlocation: refresh patch qtscenegraph-adaptation: Bump SRCREV qtsensors-sensorfw-plugin: fix build with empty QT_DIR_NAME qtvideo-node: fix package content with empty QT_DIR_NAME qtwayland: add qwayland-server-surface-extension.h, wayland-surface-extension-server-protocol.h to sync.profile, bring QWaylandExtendedSurface back for luna-next, drop patch applied in 5.9.3, refresh patches for 5.11.2 qtwebengine: add libpci to RDEPENDS, Drop patch for libEGL and libGLES2, fix filename in SRC_URI, Fix patch for additionalFeatures, refresh patches, Remove PalmServiceBridge, replace EXTRA_QMAKEVARS_CONFIGURE with PACKAGECONFIG, squash a few of chromium patches for easier maintenance recipes: drop unnecessary FILES_${PN}-dbg variables, use oe.utils.conditional instead of deprecated base_conditional sensorfw: Bump SRCREV and drop patches now merged upstream voicecall: Update to latest version from upstream webos-systemd-services: Drop installation of luna universalsearchmgr.service android-headers: Add headers for Halium-7.1, common recipe for Halium-5.1 headers, make it possible to tweak android-config.h per machine, Use Halium Headers android-headers-halium: set preferred version android-headers-tenderloin: fix patches to match Halium’s android-kernel-bootimg: dedicated recipe for creating boot.img, minimal support for A/B partitions android-system: Add missing groups, also mount /persist when it exists, cleanup old hal-hybris overlay code, don’t manage ramdisk unpacking, fix lifecycle of lxc container, Remove installation of non-existing files, simplify usage of Halium, start sensorfwd after android container, use pre-start.sh from Halium, wait a bit for the sensors to be ready android-system-image: use system.img directly, Change wop into luneos, convert the sparse image if needed, create /userdata, Update halium bits to halium version numbers base-files: use system.img directly android-tools: remove, since now in meta-oe base-files,android-system: Android partitions are now mounted by Halium’s initrd base-files: add /system/lib64 in LD_LIBRARY_PATH hammerhead, mako: Add NFC as machine feature
      Include android-kernel-bootimg for each MACHINE that needs it initramfs-android-image: make it possible to add content libhybris: provide also virtual/mesa and set PREFERRED_PROVIDER for all android devices linux-lg-{mako,hammerhead},linux-hp-tenderloin: backport 2 changes to fix build with gcc8 mako, hammerhead: Use upstream kernels which now have our patches included mako: Fix the kernel build meta-*: set PREFERRED_PROVIDER for libgl and libgbm for all android devices meta-{asus,hp,huawei,lg,motorola,oneplus,xiaomi}: remove fstab overload meta-android: initramfs-android-recovery: add inc, remove leftover from android-tools removal meta-hp: migrate tenderloin to use Halium’s init meta-oneplus: Fixes for onyx target to make build work meta-smartphone: Add meta-huawei layer with Angler target, udev-extraconf: Uniform naming scheme for device udev rules and update udev rules meta-xiaomi: add initial support for rosy (Redmi 5), Get image for Tissot building, Initial work for Xiaomi A1 (tissot), mido fix persist partition number in fstab, mido use correct wlan module name, tissot: add initramfs-android-recovery, tissot: enable permissive SELinux, tissot: ignore other parameters from bootloader, tissot: switch to cm-14.1 kernel to fix wifi Migrate LuneOS targeted machines to using android-kernel-image systemd-machine-units: fix bluetooth for hammerhead, fix bluetooth for mako The usual 1. Sign up for the bug tracker 2. Get involved and 3. Join the mailing list Download and Install Feel free to download the updated builds to get started. Tenderloin, Mako, Hammerhead and Tissot remain our focus for now, but the emulator, Mido & Rosy work too. Please note that in order to use the latest stable builds Nexus 4 (Mako) and Nexus 5 (Hammerhead) you need to flash the CM 12.1 images first using CWM/TWRP. In order to do so, you might be required to do a “factory reset” or at least “wipe cache”. CWM/TWRP will indicate when this is needed. After successfully flashing CM 12.1, make sure to boot it at least once before going back to CWM/TWRP to flash the latest LuneOS image! We have provided links to CM 12.1 for these 3 images on our device pages below. Installation instructions for TouchPad (Tenderloin), Nexus 4 (Mako), Nexus 5 (Hammerhead) and Emulator are on the wiki. And remember we don’t do timelines. Don’t forget to contact us with any questions and feel free to join the discussion on the webOS Nation forums. Catch us on Twitter @webosports on IRC: Freenode:#webos-ports or email [email protected] We will see you shortly again with a new release! Picture Credit: Chevanon. Cropped & flipped. Text added. Related posts: LuneOS July Stable Release: Cortado LuneOS February Stable Release: Chai Latte LuneOS September Stable Release: Decaf View the full article

      By pivotCE, in pivotCE News

      • 0 replies
      • 136 views
    • webOS OSE on HP Touchpad?

      With the release of webOS OSE, I'm wondering if it's able to run on the HP Touchpad. I wonder if someone will attempt to port it over.   Might give me a reason to pull out the old Touchpad, currently have an older Android system on it and haven't messed with it in over a year.

      By ajmboy, in HP TouchPad

        
      • 0 replies
      • 966 views
    • Question: LG Smart World account issues

      I have an LG Smart World Irish account. Signed in but there are very little Apps (IPTV BBC iPlayer etc..) Apps available on the Irish store. I then created a 2nd UK based account thinking it will be a workaround to getting the Apps onto the TV that I need. When I try signing in with the UK account it will not let me giving me "Cannot use this emil for the selected country. Please create another account" I switched region to uk but same issue. Changed the DNS also but still same issue. Does anybody now what the issue with this would be ? Thanks, Tony.

      By figgy, in LG webOS Smart TV App Questions

      • Awaiting best answer
      • 0 votes
      • 4 answers
    • Who Bought a Fire Sale HP Touchpad?

      Did you buy a Firesale HP Touchpad? Share the details... Thankfully, I was able to get one myself, but it took a few tries and ordering it on the HP Business site. By the time I checked all the retailer, they were gone! Snagged a 16GB for $99! I hope you grabbed one also...

      By Alex, in HP TouchPad

      • 21 replies
      • 5,072 views


×