Jump to content

Search the Community

Showing results for tags 'android'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • RVing Forums
    • Beginning RVing
    • General RV Information
    • Sharing the Fulltime Lifestyle
    • Graduating to Fulltime
    • Technical Tips and Tricks
    • Internet Access on the Road
    • Satellite TV and Radio on the Road
    • RVing on a Budget
    • Working on the Road
    • Volunteering Adventures
    • Day's End
    • Travel
    • Boondocking
    • RV Housekeeping
    • RV Action Items
    • Travel Logs
    • Escapees RV Club Events
    • Road to Escapade
    • RVing With Pets
    • RVing Families
  • RV Types
    • Class A
    • Class B
    • Class C
    • Fifth-Wheel
    • Travel Trailer
    • MDT
    • HDT
    • Bus Conversions
  • RV Marketplace
    • RV Rig Exchanges
    • RVs, Tows, and Toads for Sale
    • RV Accessories for Sale
    • RVs (And Accessories) Wanted
    • Workers Wanted
    • RVers Looking for Work
    • RV Sites/Lots/Memberships for Sale
  • Other Subjects
    • RVillage
    • Computers and Software
    • Amateur Radio
    • Activities and Hobbies
    • Veterans
    • Finances and Investing
    • Health Issues and Medical Insurance
    • Recipes
    • Other Topics
  • Site and Forum Operation
    • About the Discussion Forums
    • Bugs and Feature Requests
    • Test Posts


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL








RV Type

Found 6 results

  1. For Verizon smart phone users with Android Nougat, there is a native solution. Recents > touch the offending call > touch Details > touch the 3 dot icon (top right) > touch Block Number.I currently am blocking 60 numbers so no limit as yet.Previously I used Call Control-Call Blocker from the Google Play Store. No limit there either & works on earlier Android versions.
  2. Excerpt: "The frail world of the Android ecosystem has taken some hits in the past week with the disclosure of a full disk encryption bypass vulnerability ( https://threatpost.com/encryption-bypass-vulnerability-impacts-half-of-android-devices/119039/ ) and the arrival of the HummingBad malware. ( https://threatpost.com/chinese-ad-firm-raking-in-300k-a-month-through-adfraud-android-malware/119030/ ) The FDE bypass ( http://bits-please.blogspot.com/2016/06/extracting-qualcomms-keymaster-keys.html ) highlighted the need to keep Android patch levels current, but as Duo Labs statistics point out, that remains a struggle for Android users who must rely on carriers and handset makers to integrate and distribute Google updates. The latest Android Security Bulletin, released today, provides little relief. It’s a sizable update—late by nearly a week because of the July 4 U.S. holiday—but contains fixes for problems in a host of familiar areas including Mediaserver and a number of Qualcomm, MediaTek and NVIDIA components that have been featured in almost every bulletin since the monthly releases started last August. Patches were released to carrier and handset manufacturer partners on June 6, and Google expects source code patches to be available on the Android Open Source Project within 48 hours. Google points out that there are two security patch level strings in today’s bulletin: July 1 and July 5. “This bulletin has two security patch level strings in order to provide Android partners with the flexibility to move more quickly to fix a subset of vulnerabilities that are similar across all Android devices,” Google said. “Android partners are encouraged to fix all issues in this bulletin and use the latest security patch level string.” The July 1 patch level may include a subset of patches that are available in the July 5 patch level, which is complete. The most serious vulnerabilities are seven remote code execution flaws in Mediaserver, which are included in the July 1 patch level; July 1 also patches a critical remote code execution vulnerability in OpenSSL and Boring SSL (CVE-2016-2108). The July 5 patch level, meanwhile, patches a dozen critical elevation of privilege flaws, including a six in MediaTek drivers including the Wi-Fi driver on specific devices, as well as two in the Qualcomm GPU driver, another in the Qualcomm performance component, and one in the NVIDIA video driver. The July 5 patch level also addresses a flaw in the kernel file system (CVE-2016-3775) and in the USB driver (CVE-2015-8816). The issue of prompt Android patching has caught the attention of the U.S. government, which in May through the Federal Trade Commission and Federal Communications Commission sent letters to leading device makers and carriers seeking details on their respective security update practices. “Consumers may be left unprotected, for long periods of time or even indefinitely, by any delays in patching vulnerabilities once they are discovered. Therefore, we appreciate efforts made by operating system providers, original equipment manufacturers, and mobile service providers to respond quickly to address vulnerabilities as they arise,” said Jon Wilkins, chief of the Wireless Telecommunications Bureau at the FCC in one of the letters. “We are concerned, however, that there are significant delays in delivering patches to actual devices—and that older devices may never be patched.” Successful exploits against the full disk encryption bypass vulnerability disclosed last week require chaining together of an older, patched Mediaserver vulnerability. Duo Labs said last week that it estimates 57 percent of Android phones are still vulnerable to related Mediaserver attacks. “Compared to 60 percent of Android phones that were vulnerable to the Android attack in January, the security posture of our dataset has improved slightly, with 57 percent of Android phones vulnerable to the latest attack,” according to a Duo Labs blog post." There is a lot more especially hot links to related stories in the full article here: https://threatpost.com/android-security-bulletin-features-two-patch-levels/119056/
  3. Dell has discontinued Venue tablets with Android, and won't push out OS upgrades to current customers. Excerpt: "Dell has stopped selling Android devices as it steps away from slate-style tablets to focus on Windows 2-in-1 tablets. The company isn't refreshing the Venue line of Android tablets, and will no longer offer the Android-based Wyse Cloud Connect, a thumb-size computer that can turn a display into a PC. Other Android devices were discontinued some time ago. "The slate tablet market is oversaturated and is experiencing declining demand from consumers, so we’ve decided to discontinue the Android-based Venue tablet line," a Dell spokesman said. Although Dell has killed its Android devices, it made interesting products with the OS. One was the Venue 8 7000 tablet, which had an OLED screen and a 3D RealSense camera. Meanwhile, 2-in-1s can serve as both tablets and laptops. "We are seeing 2-in-1s rising in popularity since they provide a more optimal blend of PC capabilities with tablet mobility. This is especially true in the commercial space," the Dell spokesman said. Dell won't be offering OS upgrades to Android-based Venue tablets already being used by customers. "For customers who own Android-based Venue products, Dell will continue to support currently active warranty and service contracts until they expire, but we will not be pushing out future OS upgrades," the spokesman said. With Android devices discontinued, Dell now mostly has laptops and 2-in-1s with Windows on its roster, and some Chromebooks as well. Dell's Chromebook 11 3120 and Chromebook 13 7310 -- which run Chrome OS -- will be able to run Android apps through access to the Google Play Store. The Chromebooks won't run the Android OS, however." Much more in the whole article here: http://www.infoworld.com/article/3090544/android/dell-stops-selling-android-devices.html?token=%23tk.IFWNLE_nlt_infoworld_hardware_rpt_2016-07-07&idg_eid=6aa01e18b29f7b6f9149f611f8eac228&utm_source=Sailthru&utm_medium=email&utm_campaign=InfoWorld%20Hardware%20Report%202016-07-07&utm_term=infoworld_hardware_rpt#tk.IFW_nlt_infoworld_hardware_rpt_2016-07-07
  4. Ransomware shuts users out of their phones by changing the lock-screen password. Excerpt: "Android Nougat will come with a new security feature that prevents ransomware from locking users out of their own devices. The new operating system, slated for public release later this year, will no longer allow users or software to invoke a command that clears already-set passwords. Instead of encrypting files like traditional ransomware, Android ransomware typically resets a user's lock-screen password, preventing the user from getting access to their own phone or tablet until they pay for the password's release. Symantec's Dinesh Venkatesan, who published a write-up of the new security feature, said in a blog post that it "will not stop threats from setting the password on devices with no existing password". A developer page confirmed the "resetPassword" function can only be used to set a password if one doesn't already exist. In other words, now there's one more reason to set a password. The policy change comes amid a wave of ransomware that evolved on the platform in the past year. A number of ransomware variants have hit the platform, tricking users into installing games or utilities, which later lock users out of their devices until they pay up." More here: http://www.zdnet.com/article/android-nougat-takes-on-password-resetting-ransomware/
  5. The Android N developer preview and the Pixel C convertible tablet are Google's reference platform for competing with the iPad Pro and Surface tablets. Find out what is in store for the future of Android. Jack you may already know about these. Excerpt: "With the release of the developer preview of Android N, and a developer coupon code for 25% off the Pixel C, Google is providing developers an early look at the future of Android well in advance of Google I/O 2016—and with fewer barriers to entry than before. Users with a Nexus 5X, 6, 6P, 9, Player, Pixel C, or General Mobile 4G (Android One) device can register to receive an OTA update with the latest build of Android N, rather than manually flashing their device. Perhaps the most visible added feature in the N developer preview is a splitscreen mode, allowing users to run two apps at the same time—a prominent feature of Microsoft's Surface and Apple's iPad Pro tablets, both of which are marketed as "productivity devices." With this feature being added to Android only now (save for OEM implementations, most notably on Samsung devices), Google is playing catch-up in a big way. A brief history of Android productivity In the Android ecosystem, there is a long-standing preoccupation with attempting to sell productivity as a feature. It hasn't worked out very well thus far—the Motorola Webtop was a revolutionary "dockable Android" that converted into a theoretically usable desktop interface. This was limited by the relative lack of processing power and RAM available to smartphones at the time, like the Droid Razr Maxx, and was swiftly discontinued after Google bought Motorola. Other peculiar-though-unique attempts at productivity devices include the foldable Sony Tablet P and pico-projector wielding Samsung Galaxy Beam. While the aforementioned phones are now roughly four years old, it is also worth mentioning the checkered past of Android on full-size tablets. Motorola Xoom, the first true Android tablet, had only 19 months' worth of version updates. The Nexus 10 fared much better, though the vaguely oval device shape was never seen again. The Nexus 9 got great reviews from CNET, though early models had manufacturing issues that were swiftly corrected. Ultimately, this is all in the past, and Google's obvious message is that the Pixel C represents the future. Pixel C and Android N: A splitscreen adventure Although Android N brings splitscreen to all the test devices (counting picture-in-picture on the Nexus Player), the most obvious immediate beneficiary of this is the Pixel C. The unique screen ratio of 1:√2 (a resolution of 2560x1800) prevents splitscreen apps from feeling cramped, as opposed to the squeeze on 16:9 displays intended for media consumption. Presently, the splitscreen mode allows the use of only two apps at a time. If you hold the Pixel C horizontally (or are using the Bluetooth keyboard), the apps are split to each side, while in vertical orientation they're split to the top and bottom of the screen. Although this is still only a developer preview, things tend to work rather well with Gmail and Chrome. Best candidate for "Top Android Tablet"? The Pixel C is a stunning device, and in comparison to its Nexus-branded forerunners, the most premium-looking Android tablet yet. The Pixel line is very much the "aspirational" reference product for Android OEMs to draw inspiration from. Conversely, the Pixel C is also the reference device for Google developers to tailor the Android experience to tablets. The Pixel C is a malleable device—the promise of software updates about six weeks, as mentioned in the announcement in September, is absolutely being fulfilled." The article there starts showing the screenshots and goes on to cover another several pages of information and reviews about the productivity efforts that Android is doing to keep an oar in the water, here: http://www.techrepublic.com/article/pixel-c-and-android-n-the-future-of-productivity-on-android/?ftag=TRE684d531&bhid=19724681974700635514865380622813
  6. Before everybody attacks the messenger, here are excerpts and the link. Good article, really! Excerpt: "With no solid business productivity apps, as well as continually perpetuating the 'toxic hellstew', Google's mobile OS is still missing from my personal tech stable two years after I abandoned it. But there's some hope for it yet. This morning, I read with some amusement my colleague David Gewirtz's article The year Microsoft lost my loyalty. I'm not going to attempt to refute his conclusions, because whatever reasons David has for choosing his particular mix of technology is unique to his own situation. Gewirtz is not the only ZDNet contributor to forsake a technology, or a technology vendor, when it comes to their own bag of stuff they use every day. In March 2012, I publicly called it quits with Android. This raised a bit of a stir, that coming from such a long history of being an open-source advocate I would forsake a platform I had spent so much time using and was so philosophically aligned with. Of course, as memory serves, I joined Microsoft later that year. To the causal observer (translation: Mouth-breathing fanboy), it would seem my newfound gripes with Android would have something to do with my newfound employment. Nothing could be further from the truth. My romance with Google's mobile operating system had been souring for quite some time while I was still at IBM. You know, that "We're spending another billion dollars on Linux" company that now apparently has a thing for iPads. Things began to go sour with me and Android in 2011, which I referred to at the time as the year of Android multiple personality disorder. In 2011, Android handsets and tablets ran on totally different OS builds, Gingerbread and Honeycomb. The overall poor quality of the hardware, as well as the horrible stability of the Android tablets of this period, was a reflection on this situation, which was eventually proven to be untenable. Prior to this development, my ZDNet colleague Adrian Kingsley-Hughes' "Toxic Hellstew" was simply a spicy broth that might give an unfortunate diner a bad case of heartburn. A particularly potent Bún bò Huế, if one was to use a culinary analogy. But my tummy ache was only just beginning." The very interesting article goes on from there. Good read here: http://www.zdnet.com/article/2014-still-sick-of-android/?tag=nl.e539&s_cid=e539&ttag=e539&ftag=TRE17cfd61
  • Create New...