-
Similar Topics
-
By Harald Dunkel
Since 4 weeks my TV (OLED55BX9LB) nags me I should replace the batteries in the magic remote. Is there some way to disable this annoyance? The batteries are still fine.
-
By Peter94
I use BT Headphone with LG OLED C1 TV Webos 6. It would be nice if I could also see its battery level next to volume level on the screen
-
By News Reporter
While every webOS device comes with some kind of speaker, the TouchPad is the only one whose speaker is adequate to fill a (smallish) room. On the phones, even the rear speaker struggles to put out enough volume to allow sharing of music or other audio in a space with moderate or higher background noise. Given that webOS phones all support both standard 3.5mm headphone/speaker jacks (the Veer admittedly needing an adapter) and Bluetooth speakers, there are numerous options for boosting the sound so others can enjoy it too. Unfortunately, most of those external speakers are far less portable than the phone itself. There are, though, some speakers that offer both powered amplification and portability. One of these is the Naztech N15 3.55 Mini Boom Speaker, which additionally operates as a standalone MP3/WMA player (it accepts microSD cards as removable storage, and has minimal controls for music playback and track navigation). While the Naztech's design and standalone player capabilities are pluses, however, its minimal amplification power makes it a poor choice for webOS devices.
Naztech has done a nice job with the design of the N15. It folds to the size and shape of a flattened golf ball, with a recess for storing the non-removable (and very short at 2-3 inches) 3.5mm audio cable. Along the periphery of the speaker are the standalone music player controls, a miniUSB (not microUSB, unfortunately, meaning it cannot share charger cables with a webOS device) port, and the microSD slot. The play/pause button doubles as the power button for the speaker, and a blue LED lights up when the unit is powered on. Note that although the track forward and reverse buttons double as volume controls for standalone play, they do not affect volume when the N15 is connected to an external sound source. According to Naztech, the N15 provides 2 watts of speaker output, and its 3.7 volt lithium ion battery charges (via a powered USB port or charger) in 4 hours. Naztech does not provide any play time details, and our testing did not extend to battery life.
link hidden, please login to view
-
By News Reporter
The screen on your webOS device is the primary way for you to interact with your device, but it's also a big battery drainer. You can easily
link hidden, please login to view, but you can also set the length of time that it will take before webOS automatically turns off the screen. If you go into the Screen & Lock app, you can set the "Turn off after" option to 30 seconds or 1, 2 or 3 minutes on webOS phones, or 1, 2, 5 or 10 minutes on the TouchPad. There are also patches available in Preware that will give you additional screen timeout options. You want to find the timeout setting that works best for you. Adjusting the setting for too long of a time will potentially cause the screen to be on longer than necessary, thereby draining the battery faster than you needed and may even cause unintentional screen taps. But selecting too short of a setting may cause the screen to turn off before you want it to, such as when you are reading a long article or while thinking of what to write in a document or email. Regardless of the setting, you will notice that the screen will dim first after a short period of time, giving you a little warning before the screen will turn off all the way. All you need to do is tap the screen or anywhere in the of phones to reset the clock for the screen timeout.
Also, note that some apps may override your screen timeout setting. If you are watching a video or playing a PDK game, the screen may stay on indefinitely. You will need to manually press the power button to shut off the screen in these situations, or minimize the app to card mode to allow the auto-shut off to occur.
-
By News Reporter
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
link hidden, please login to view. 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 that is a staple point of . 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 . 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 ), 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 .
-
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.