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


  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 1,204 results

  1. I have started this sub-section for Android Games to keep Android mobile games free from applications / themes. All nsane members are requested to post Games here. If admins as requested creates a sub-forum for it at any stage, this thread will be merged later. For posting guidelines, please refer to this post: //www.nsaneforums.com/topic/220597-guidelines-and-templates/ PS: Admin, thanks for listening to Android sub-forum request.
  2. A new set of 25 Android apps caught illegally charging users at the end of a trial period. Security researchers from Sophos say they've discovered a new set of "fleeceware" apps that appear to have been downloaded and installed by more than 600 million Android users. The term fleeceware is a recent addition to the cyber-security jargon. It was coined by UK cyber-security firm Sophos last September following an investigation that discovered a new type of financial fraud on the official Google Play Store. It refers to apps that abuse the ability for Android apps to run trial periods before a payment is charged to the user's account. By default, all users who sign up for an Android app trial period, have to cancel the trial period manually to avoid being charged. However, most users just uninstall an app when they don't like it. The vast majority of app developers interpret this action -- a user uninstalling their app -- as a trial period cancelation and don't follow through with a charge. But last year, Sophos discovered that some Android app developers didn't cancel an app's trial period once the app is uninstalled and they don't receive a specific request from the user. Sophos said it initially discovered 24 Android apps that were charging obscene fees (between $100 and $240 per year) for the most basic and simplistic apps, such as QR/barcode readers and calculators. Sophos researchers called these apps "fleeceware." In a new report published yesterday, Sophos said it discovered another set of Android "fleeceware" apps that have continued to abuse the app trial mechanism to impose charges to users after they uninstalled an app. These apps were installed by more than 600 million users. The number seems high, but Sophos mobile malware analyst Jagadeesh Chandraiah said he suspects the apps might have used third-party pay-per-install services to boost install counts and then bought fake five-star reviews to boost their ranking on the Play Store and attract a large number of users. It's very likely that not all users who installed these apps signed up for a trial period, but those who did might want to check their Play Store payment history for any charges coming from past, now-uninstalled apps. The table below contains the names and other indicators for the 25 Android apps which Sophos says are engaging in fleeceware behavior. One of the apps -- the GO Keyboard Lite keyboard app -- has a history of shady behavior. Back in 2017, this app was caught sending back the text users were typing on their devices to servers in China. Source
  3. Quick Tip Today am gonna show you how you can download your favorite Android Apps directly from Google Play Store. From the Play Store, search for your favorite app, copy the link with the app id visit apps.evozi.com/apk-downloader/ Paste the link and click generate download link. Wait for some seconds as your download link is been generated. After some few seconds, your link should be ready for download. eNJOy!!! source: thetechblog
  4. Open letter from 50+ organizations want Google to do something about Android bloatware Over 50 organizations including the Privacy International, Digital Rights Foundation, DuckDuckGo, and Electronic Frontier Foundation have written an open letter to Alphabet and Google's CEO Sundar Pichai about exploitive pre-installed bloatware on Android devices and how they pose a privacy risk to consumers. The open letter says that all Android OEMs pre-install their devices with apps that cannot be deleted and that due to their privileged custom permissions, they can bypass the Android permission model. This allows them to gain access to the microphone, camera, and location without user intervention. This has led many smartphone OEMs to collect user data without their explicit permission and use it for their benefit. Thus, the group wants Google to make some changes to how Android handles pre-installed apps a.k.a bloatware. They want the company to provide users with the ability to permanently uninstall all pre-installed apps on their devices. While some pre-loaded apps can be disabled on Android devices, they continue to run some background processes which makes disabling them a moot point. The open letter requests Google to ensure that pre-installed apps go through the same scrutiny as all the apps listed on the Google Play Store. They also want all pre-installed apps to be updated through Google Play even if the device does not have a user logged into it. Google should also not certify devices on privacy grounds if it detects that an OEM is trying to exploit users' privacy and their data. Google made a number of privacy-focused changes in Android 10 but there's a lot the company can still do to secure the platform and keep users safe from pre-installed apps that exploit their data. Source: Open letter from 50+ organizations want Google to do something about Android bloatware (Neowin)
  5. Apps spotted abusing use-after-free() bug seven months before patch At least three malicious apps with device-hijacking exploits have made it onto the Google Play Store in recent weeks. This is according to eggheads at Trend Micro, who found that the since-removed applications were all abusing a use-after-free() flaw in the operating system to elevate their privileges, and pull down and run further malware from a command-and-control server. The malicious apps were Camero, FileCrypt, and callCam, so check if you still have them installed. "The three malicious apps were disguised as photography and file manager tools," said Trend researchers Ecular Xu and Joseph Chen on Monday. "We speculate that these apps have been active since March 2019 based on the certificate information on one of the apps." The exploited programming blunder was CVE-2019-2215, a use-after-free() vulnerability present in the inter-process messaging system of the Android kernel, specifically in binder.c. Successful exploitation of the flaw allows a local app to execute arbitrary code on the infected gizmo with kernel-level privileges, aka God mode. It is not clear how many times the apps had been installed, though the reach may have been minimal as a screencap for Camero lists its installs at "5+". Interestingly, while the apps themselves have been available since March 2019, the fix for CVE-2019-2215 was only posted in the October 2019 Android security update. However, the exploit for that vulnerability may have been added after March, such as when the hole was first disclosed. According to the researchers, exploitation occurred when a victim downloaded either Camero or FileCrypt Manager. The supposedly legitimate apps contacted a command and control server from which they download a pair of files that, in tandem, exploited CVE-2019-2215 to gain kernel-level privileges and installed the final piece of the scheme, the callCam app. The callCam tool is able to collect device hardware information as well as location, installed apps, and data from specific applications like WeChat, Outlook, Twitter, Yahoo Mail, Gmail, and the Chrome browser. The pilfered data is then stored as an encrypted file for upload at a later time. It is believed that, based on the command and control servers, the group behind the infections is the SideWinder crew, a hacking operation active since 2012. The team is believed to have largely targeted government and military systems in Pakistan and has until now relied mostly on exploits and malware for Windows PCs. Source
  6. Microsoft Edge Beta gets its new icon on Android Microsoft is beginning to make the new icon for its Edge browser more widely available, as it's shown up on the beta version of the Android app today. there aren't any other new features like we saw earlier this week; it's just the new icon. The company is preparing for the big desktop launch of Edge Chromium, the new version of its in-house browser. Beginning on January 15, the new browser will be generally available; not only that, but users on Windows 7, Windows 8, Windows 8.1, and macOS will have access to Edge for the first time. And of course, it will have a new logo to differentiate from Edge Legacy. An update to Edge Beta on Android, which has always been based on Chromium, was offered earlier this week to let people choose whether to sync with "The new Microsoft Edge" or "Microsoft Edge Legacy", rather than Edge Insider and Edge. It also introduced a new Control Center. It's unclear when the new icon will show up in the production channel or when it will be available on iOS, but some time around January 15 sounds like a sure bet. Source: Microsoft Edge Beta gets its new icon on Android (Neowin)
  7. Outlook is the latest Microsoft Android app to pass 100 million installs on the Play Store The latest Microsoft app tom hit the 100 million install mark on the Google Play Store is Outlook, as was spotted by MSPU over the weekend. It joins apps like Word, Excel, PowerPoint, OneDrive, Skype, OneNote, and SwiftKey in the club. Those apps have many more installations though, as Word, Excel, PowerPoint, Skype, and OneDrive all have over a billion installations, while OneNote and SwiftKey have 500 million. Microsoft's Frank X. Shaw noted back in April that Outlook has 100 million users on iOS and Android. However, that's counting users, while the Google Play Store is counting installations. It's also worth noting that the Google Play Store doesn't account for all Android devices. Amazon offers Outlook on its own app store, as do other vendors. The next milestone for Outlook to hit in the Google Play Store will be 500 million, since Google doesn't count anything in-between that and 100 million. Microsoft is always continuing to improve the product, as well as making deals with OEMs to get Outlook preinstalled. Naturally, it will also be preinstalled by default on the upcoming Android-powered Surface Duo. Source: Outlook is the latest Microsoft Android app to pass 100 million installs on the Play Store (Neowin)
  8. Edge Beta on Android now lets you choose between sync with Edge Chromium or Edge Legacy We're now just a couple of weeks away from the January 15 launch of Microsoft's new Chromium-based Edge browser. The company is prepping for launch, now updating the beta version of Edge on Android so that you can choose whether to sync with the new one, or the EdgeHTML-based Edge Legacy. This option was already available, but it specifically referred to the Edge Insider channels for the new version, and to the legacy version simply as Microsoft Edge. It also notes that "The new Microsoft Edge" will not sync with Edge Legacy, which is no surprise. Edge Chromium will start off by importing all of your favorites, passwords, and so on from either Edge Legacy or another browser that you might have on your PC. The assumption is that you're not using Edge Legacy, because frankly, most people aren't. There's also a new Control Center included in the browser on Android, which was initially spotted in late October. Tapping on the ellipsis in the new navigation bar will bring up the menu with a variety of options. Edge Chromium will launch on Windows in a couple of weeks, and it will support Windows 7, Windows 8, Windows 8.1, and Windows 10, along with macOS. That means that many users will be able to sync their mobile Edge browser to the desktop for the very first time. Source: Edge Beta on Android now lets you choose between sync with Edge Chromium or Edge Legacy (Neowin)
  9. Microsoft confirms Cortana for iOS and Android killed off everywhere except USA, reveals when Surface Buds are coming Speaking to VentureBeat, Microsoft’s Andrew Shuman, the successor to Javier Soltero and Corporate Vice President for Cortana, confirmed that Cortana for iOS and Android would be withdrawn from all international markets except USA. Microsoft has previously announced that the app will no longer be supported in only 8 countries, Australia, Canada, China, Germany, India, Mexico, Spain, and the U.K. Microsoft said the US would be an exception for two reasons – one to allow Surface Headphone and Harmon Kardon Invoke users to configure and update the firmware of their headphones, which uses the Cortana app, and secondly to allow Microsoft to continue to experiment with the technology. These Surface Headphones also sold outside the USA, but international users will need to use Cortana for Windows. Microsoft did say they are releasing a Surface Audio app for Windows, iOS and Android, with the Surface Buds in Spring next year which will, however, take over the functions of Cortana. As mentioned earlier, Microsoft also wanted to keep a toe in the mobile market. “We also think that there may be some roles for standalone assistants as an experimentation place for us to try out new ideas still. I think this point has been made a lot, but … the assistant landscape is rich with opportunity, and very not rich with actual results, sometimes. And so the opportunity to continue to try things quickly is important to us as well.” Microsoft confirmed that they were still investing on the desktop in Cortana/Alexa integration. “We still have a great aspiration to do a lot more … kind of across the two companies,” he said. “It started really tops down. I don’t know if you remember that, but Satya [Nadella] and Jeff [Bezos] actually cooked this plan up. You can still invoke Cortana from Alexa, and vice versa. I think it will be a great area for us to lean into. We really believe in a multi-assistant world. Just like in the real world where I might have a doctor, and a lawyer, maybe a trainer, you’re going to have multiple assistants that are good at what they’re good at. We’re not going to become an ecommerce company anytime soon, but assistants are great at helping you buy things.” Microsoft was also working on Cortana text-based natural language input. “One of the things that we’re investing in Windows is this idea of being a quicker experience for people who are good typists. Those of us who’ve been around computers for a while don’t need to talk to them. But still, the power of natural language is really great. I’ll give you one example that I use now all the time on the builds I’m running, which is just managing my time in my calendar. It’s a lot easier to type in ‘dentist appointment next Friday’ than to alt-tab to Outlook, new file, tab, tab, tab, type in ‘dentist,’ type in ‘Friday,’ and find a free time. So that’s a great example, where just getting data into and out of my digital calendar is really simplified by natural language understanding.” Lastly, Microsoft was looking at adding Cortana integration to most of their Office apps. “The analogy that I like to use is both Microsoft Search or Microsoft Account, which are really across all of our applications,” said Shuman. “We think of Cortana in a very similar way, where it really is a horizontal surface area that’s very person-centric. It very much knows a lot about me, and then it experiences itself across all of these apps and suites. So that’s the way that we characterize the investment moving forward. And partially, that’s just the reality of wanting to be in the experiences you’re using every day and not [having] to switch over to another one to get the experience.” “Obviously, there’s strength in enterprises, but the kind of problems we have are very universal,” he continued. “It’s about helping people get time back. The previous apps that we were showing before were really great when we were in startup mode and trying to sort out what an assistant could be. But they were not directly aligning with those Microsoft 365 users who really don’t want to go to another experience to do their stuff. They want to be able to do it in the apps they’re using every day, like Outlook and like Teams. That’s really been our push now — over a year now of work that we’ve had underway.” Microsoft’s ambitious for their voice assistant has clearly reduced, but as a modern Clippy it may just have found its niche. “That’s the kind of thing that’s truly important about an assistant. An assistant has to really know you. And that’s absolutely core to why we’re having this renewed focus on these users that we think we can offer the most value to.” Source: Microsoft confirms Cortana for iOS and Android killed off everywhere except USA, reveals when Surface Buds are coming (MSPoweruser)
  10. Google devs "forgot" to move some user data during the Chrome 78 to Chrome 79 update process. Google has halted the rollout of Chrome 79 on Android after mobile app developers reported a major bug that was deleting user data and resetting mobile apps. The bug occurred during the update process from Chrome 78 to Chrome 79. In Chrome 79, Google developers changed the location of the Chrome directory. In a bug report filed last week, Google developers admitted to making a mistake with this operation and forgetting to move the contents of localStorage or WebSQL into the new Chrome 79 directory, making the data inaccessible for all users. localStorage and WebSQL are widely used in mobile apps Both localStorage and WebSQL are storage mechanisms that allow a website or web app to store data on a user's device, inside a user's Chrome profile directory. While some websites use localStorage or WebSQL, most prefer to use dedicated database servers to store user data on the server-side. However, localStorage and WebSQL are widely used on mobile devices, and especially by mobile app developers. These days, many Android apps are nothing more than a website loaded inside the WebView component -- a stripped-down version of Chrome. These apps heavily depend on mechanisms like localStorage or WebSQL to save settings and user data locally, instead of using a separate and bulkier SQLite database. When Chrome 79 started rolling out, these apps lost access to all the files and data saved inside the old Chrome 78 localStorage and WebSQL folders. App users lost data, settings, files, and even access to their accounts. "When I say 'broken,' I mean that their encrypted login information has been wiped and they can't remember their credentials (and resetting them are practically impossible in the case of our app)," said the developer of a mobile cash management app. In his case, over 250,000 users have been affected already, with two million more facing a similar problem in the coming days. However, he is not alone. There are countless other Android app developers who are facing similar issues. And for good reasons, app users are getting angry. Unfortunately, they're getting angry at the wrong persons -- namely, the app developers, not knowing this is a Chrome issue. "My app currently get[sic] review bombed with 1-star ratings because all users lose[sic] currently all stored data," said another app dev on Reddit. A fix is not 100% guaranteed to save restore user data Chrome 79 was released on Tuesday, December 10. A first bug report was filed on Thursday, and Google stopped the Chrome 79 rollout on Android on Saturday. Unfortunately, the update already reached around 50% of the Android userbase, meaning it already caused quite a lot of breakage. Google developers are currently working on an update that fixes the data migration process, but for many, this might be too late. Even Google developers don't know if the older localStorage and WebSQL files were left behind, or the Chrome update process wiped the data. In some cases, "cleaner aps" might have deleted the data after the update operation. Further, moving the old files to the new location might end up overwriting new files the user has created in the meantime, leading again to data loss. A solution for the bug is still being discussed on the Chromium bug tracker. Source
  11. Google introduces Verified SMS and spam detection in Android Messages Google has been trying to upgrade the messaging experience for SMS for some time through RCS (Rich Communication Services), a technology that's finally rolling out more broadly in the U.S. Today, though, the company is improving SMS in a different way - by increasing security. Through a new blog post, Google announced the rollout of a new feature called Verified SMS, which lets users know when they're receiving messages from a real business. The reason this needs to exist is that many businesses send out SMS, like verification codes, from random numbers, which makes it easy for users to be deceived by impersonators. This new feature will verify whether a specified message is truly from a business. This feature is rolling out in nine countries for now: the U.S., India, Mexico, Brazil, the UK, France, Philippines, Spain, and Canada, but more countries will be added over time. Another new feature, at least for some users, is real-time spam detection, and it does exactly what the name implies. The Messages app will warn you if it thinks a message might be spam, and you can confirm or deny its suggestions, which also helps improve Google's algorithm. This feature has already been available for the past year in some countries, but it's rolling out more broadly in the United States now. If you're in the U.S. and you're worried about security, Google also recently hardened the security of its Fi service, expanding features like spam warnings for calls and VPN to more phones. Source: Google introduces Verified SMS and spam detection in Android Messages (Neowin)
  12. Opera 55 Stable for Android is out: here is what is new Opera Software released a new stable version of the web browser on December 5, 2019. The new Opera 55 web browser for Android devices includes a new Night Mode and improved keyboard dimming functionality. The new version of the mobile web browser should be offered to Android users soon via Play Store updates. It may also be downloaded from Google Play (and other sources) manually. The major new feature of Opera 55 for Android is the browser's redesigned Night Mode. It is disabled by default but may be activated with a tap on the Opera icon and the toggling of Night Mode in the menu. You may customize Night Mode functionality in the browser's settings. Just tap on Night Mode there to open the configuration page. There you find the following options in Opera 55: Change the color temperature to alter blue light emission. Change the dimming. Toggle the use of the dark theme. Enable dark web pages. The feature enables a dark theme for sites that don't support dark themes by default. Enable the new dim keyboard feature; this requires an additional permission as the browser uses an overlay to dim the keyboard on the device. Schedule Night Mode so that it is enabled during a specific period, e.g. from sunset to sunrise or custom period. With Night Mode enabled, Opera for Android will display webpages that are opened in the mobile browser accordingly. It makes sense to use Night Mode together with Dark Mode on the deice and the extra dark web page and dim keyboard modes. All taken together paint the entire screen in darker colors that may make the whole experience more enjoyable in the morning and at night, and may also improve sleep. Opera Software calls it Super Dark Mode when all Night Mode features are enabled. The browser takes care of the UI, webpages, and keyboard that may be displayed when it is active. Source: Opera 55 Stable for Android is out: here is what is new (gHacks - Martin Brinkmann)
  13. Vivaldi releases second Beta of its Android browser Vivaldi Technologies, the company behind the Vivaldi web browser, released the second Beta of the upcoming Vivaldi mobile browser for Android on December 5, 2019. The company released the first, long-awaited, version of its Android browser back in September and has been working on improvements since then. The new version is already available on Google Play. Users who have installed the previous beta may notice that it is updated automatically eventually; users who don't want to wait can force the update in the Google Play application or the browser's Play Store webpage. Vivaldi Beta 2 for Android is a big update that introduces new features and changes to the mobile browser. As is the case with most Vivaldi updates, a lot of development time went into improving the browser's usability. Users of the Android version of Vivaldi find a whole assortment of new features in the Settings: Swipe to close tab -- Can be enabled in the Settings to quickly close open tabs in the Tab Switcher by swiping them to the left or right of the screen. Show scrollbars on internal pages -- The option displays scrollbars on Vivaldi's internal pages which provides a position indicator. Always show desktop site -- When enabled, tries to load the desktop version of visited sites automatically instead of mobile pages. But there is more. It is now possible to delete all bookmarks and notes marked for deletion with a single tap on the "empty trash" icon. The browser's Start page received several improvements as well. Vivaldi added drag & drop support to the Speed Dials to allow them to be rearranged by the user. A long-tap displays a context menu with options such as edit or delete, and a tap on the plus icon adds a new Speed Dial to the current folder. The Vivaldi Search widget may be placed on the home screen to run searches directly from it (without opening Vivaldi first). Additionally, there is support for running the beta 2 of the browser on Chromebooks, improved stability, and thinner icons in the UI. Closing Words It is too early to give a final verdict but if Vivaldi Technologies manages to add as many features and options to the Android version as it has added to the desktop version, it could easily become as successful. Not all Internet users want customizations and options but those who do, may have something to look forward to. Source: Vivaldi releases second Beta of its Android browser (gHacks - Martin Brinkmann)
  14. Vulnerability in fully patched Android phones under active attack by bank thieves "StrandHogg" spoofing flaw exploited by 36 apps, including bank trojans. Enlarge portal gda / flickr A vulnerability in millions of fully patched Android phones is being actively exploited by malware that's designed to drain the bank accounts of infected users, researchers said on Monday. The vulnerability allows malicious apps to masquerade as legitimate apps that targets have already installed and come to trust, researchers from security firm Promon reported in a post. Running under the guise of trusted apps already installed, the malicious apps can then request permissions to carry out sensitive tasks, such as recording audio or video, taking photos, reading text messages or phishing login credentials. Targets who click yes to the request are then compromised. Researchers with Lookout, a mobile security provider and a Promon partner, reported last week that they found 36 apps exploiting the spoofing vulnerability. The malicious apps included variants of the BankBot banking trojan. BankBot has been active since 2017, and apps from the malware family have been caught repeatedly infiltrating the Google Play Market. The vulnerability is most serious in versions 6 through 10, which (according to Statista) account for about 80% of Android phones worldwide. Attacks against those versions allow malicious apps to ask for permissions while posing as legitimate apps. There's no limit to the permissions these malicious apps can seek. Access to text messages, photos, the microphone, camera, and GPS are some of the permissions that are possible. A user's only defense is to click "no" to the requests. An affinity for multitasking The vulnerability is found in a function known as TaskAffinity, a multitasking feature that allows apps to assume the identity of other apps or tasks running in the multitasking environment. Malicious apps can exploit this functionality by setting the TaskAffinity for one or more of its activities to match a package name of a trusted third-party app. By either combining the spoofed activity with an additional allowTaskReparenting activity or launching the malicious activity with an Intent.FLAG_ACTIVITY_NEW_TASK, the malicious apps will be placed inside and on top of the targeted task. "Thus the malicious activity hijacks the target's task," Promon researchers wrote. "The next time the target app is launched from Launcher, the hijacked task will be brought to the front and the malicious activity will be visible. The malicious app then only needs to appear like the target app to successfully launch sophisticated attacks against the user. It is possible to hijack such a task before the target app has even been installed." Promon said Google has removed malicious apps from its Play Market, but, so far, the vulnerability appears to be unfixed in all versions of Android. Promon is calling the vulnerability "StrandHogg," an old Norse term for the Viking tactic of raiding coastal areas to plunder and hold people for ransom. Neither Promon nor Lookout identified the names of the malicious apps. That omission makes it hard for people to know if they are or were infected. Google representatives didn't respond to questions about when the flaw will be patched, how many Google Play apps were caught exploiting it, or how many end users were affected. The representatives wrote only: "We appreciate the researchers['] work, and have suspended the potentially harmful apps they identified. Google Play Protect detects and blocks malicious apps, including ones using this technique. Additionally, we're continuing to investigate in order to improve Google Play Protect's ability to protect users against similar issues." StrandHogg represents the biggest threat to less-experienced users or those who have cognitive or other types of impairments that make it hard to pay close attention to subtle behaviors of apps. Still, there are several things alert users can do to detect malicious apps that attempt to exploit the vulnerability. Suspicious signs include: An app or service that you're already logged into is asking for a login. Permission popups that don't contain an app name. Permissions asked from an app that shouldn't require or need the permissions it asks for. For example, a calculator app asking for GPS permission. Typos and mistakes in the user interface. Buttons and links in the user interface that do nothing when clicked on. Back button does not work as expected. Tip-off from a Czech bank Promon researchers said they identified StrandHogg after learning from an unnamed Eastern European security company for financial institutions that several banks in the Czech Republic reported money disappearing from customer accounts. The partner gave Promon a sample of suspected malware. Promon eventually found that the malware was exploiting the vulnerability. Promon partner Lookout later identified the 36 apps exploiting the vulnerability, including BankBot variants. Monday's post didn't say how many financial institutions were targeted in total. The malware sample Promon analyzed was installed through several droppers apps and downloaders distributed on Google Play. While Google has removed them, it's not uncommon for new malicious apps to make their way into the Google-operated service. Update: In an email sent after this post went live, a Lookout representative said none of the 36 apps it found was available in Google Play. Readers are once again reminded to be highly suspicious of Android apps available both in and outside of Google Play. People should also pay close attention to permissions requested by any app. Source: Vulnerability in fully patched Android phones under active attack by bank thieves (Ars Technica)
  15. An early look at Firefox Preview 3.0 for Android Mozilla released the first beta version of Firefox Preview 3.0 on the project's GitHub home. The beta, which is only available on GitHub and not on Google Play, upgrades the mobile browser for Android to version 3.0. Firefox users who want to test the new browser using a version from Google Play may download the Nightly version instead. Note that Nightly versions are development builds that may be unstable. Mozilla started to work on Firefox Preview, initially known as Fenix, some time ago. We covered the first public release of Firefox Preview in 2019 and the launch on Google Play. The organization plans to replace the current version of Firefox for Android with Firefox Preview (and rename Firefox Preview to just Firefox once that is done). Firefox Preview 2.0 was released some time ago. The version, available on Google Play and GitHub, introduced support for a number of features including send tab to other device, more browsing data clearing controls, or options to add website shortcuts and a search widget to the Home screen of the device. Firefox Preview 3.0 introduces major new features that extend the functionality significantly. The new version includes options to add search engines manually to the Firefox browser, control autoplay behavior, and adds better enhanced tracking protection and syncing controls. Enhanced Tracking Protection improvements: switch between standard and strict protection settings and better manage the feature. Open links in private tabs: option to open any link in a private tab in Firefox Preview. (tap on the link you want to open, select Firefox Preview, pick always). Clear browsing data on exist: a new Setting to clear browsing data on exit is available in Firefox Preview 3.0. Previously, it was only possible to clear the data manually (only works when you select the quit option from the menu). Choose what to sync: currently, you may select Bookmarks or History only. Option to control media autoplay: was not available in the beta version that I used. List and manage downloads. Ability to add search engines manually. Put the navigation bar at the top or bottom of the browser interface. Enforce zoom on all websites. The browser lacks add-on support at the time but Mozilla promised that Firefox Preview would support extensions after all. Support for some extensions is expected to become available in the first half of 2020. Closing Words Firefox Preview is improving with every release but that is usually the case before the first final release of a product. Mozilla wants to ensure that all major features of the current Firefox version for Android are supported by the upcoming browser before users are switched over to the new browser. Source: An early look at Firefox Preview 3.0 for Android (gHacks - Martin Brinkmann)
  16. Facebook Viewpoints lets you make money by giving the company more data Facebook has announced Viewpoints, a new app for Android and iOS that lets users get monetary rewards for participating in different kinds of user research programs, such as surveys. The platform will offer a number of programs over time, requesting to collect certain information about the user. Rewards are given out as points, and when a user gather enough points, they can be turned into money that's sent to the user's PayPal account. To kick off the Viewpoints app, Facebook is launching a well-being survey, which aims to help the company create products that "limit the negative impacts of social media and enhance the benefits". This research is worth 1,000 points, which is equal to US$5. Facebook isn't in a particularly good position to be asking users for more data, but it tried to ease the concerns of those worried about their privacy. For each program, Viewpoints will tell the user what information will be collected and how it will be used before the user registers for it. The Viewpoints app itself will ask for the user's name, age, gender, country of residence, and e-mail address. Facebook says this information will be used to improve the company's own products and that it won't be sold to third parties. Viewpoints activity won't be posted to Facebook without the user's permission, and, of course, users can quit anytime. If that's enough to ease your fears, you can download Viewpoints for Android or iOS to start completing the first program. You can learn more about the app here. Source: Facebook Viewpoints lets you make money by giving the company more data (Neowin)
  17. Google Photos markup feature begins rolling out to all users Google Photos has recently been receiving updates that aim at improving user experience and bringing in nifty features. One such feature that was spotted by a few users was the ability to markup images on Google Photos. As the name suggests, the feature provides users with simple tools to draw on images. However, not many devices saw this update, and there was no way to force install it. Now, a small post on the Google Photos Support forum suggests that the feature is rolling out to all Android users. Accessing the tool is straight forward since the Markup icon is present right in the editing interface. It provides users with the option to choose from a list of colors and two types of brushes. For those that are accustomed to using the Photos app for quick editing, this feature will indeed be a welcome addition. There is a separate support page with more details on using the editing tools in Photos. In addition to these small improvements, reports suggest that the firm is also testing the ability to manually tag faces in Photos for when automatic tagging fails to recognize a person. This feature was confirmed to be in the roadmap for the app earlier this year. The markup tool is currently rolling out to users worldwide. The feature might not show up right away to all users and may be a while till every device received the update since it is staggered. Source: Google Photos markup feature begins rolling out to all users (Neowin)
  18. MSPU Tips: Here is how to use your Android smartphone as a means to send texts to your Windows 10 PC and other devices We’re on the cusp of 2020 and most of us are carrying multiple devices, each serving different purposes. And since tech companies are still far from being able to make the “One device to rule them all” idea a reality, it only makes sense for the companies to find a solution that helps users make their devices work together. Apple has done it, Microsoft has done it, and Google is doing it. You can now use your Android smartphone as a means to send texts or webpages to devices that are linked to your Google account. The process is simple and easy. All you have to do is select a text and then hit the share option, you’ll then see an option called “Send text to Your Devices,” the logo of which is of Google Chrome browser. Now, click on the option and it will then display a “Send to” sheet, containing the list of devices that are liked your Google account. You need to select the device you want to send the text to. Tap and hold on a text field that appears on the device you just send the text to, choose the option paste. You can now see the result. You’ll be able to paste text on smartphones, PCs, Macs, iOS devices, and any device that has a screen and is connected to your Google account. Note, the device from which you’re sending the text and the device you’re sending the text to need to be tied to a similar Gmail account in order for this feature to work. Similarly, you can send URLs to devices that are linked to your Google account. The process is exactly the same! It’s also worth noting that you’ll also be able to send texts from your Outlook email app on Android, meaning that sending texts doesn’t require you to open Google Chrome. This is Google’s answer to Microsoft’s Cloud clipboard feature in Windows 10, though I’d argue that Google’s solution is way better than Microsoft’s Cloud clipboard. If you want to copy something on your PC and then want to paste it to a non-Windows 10 device, Microsoft’s Cloud clipboard won’t help you. Microsoft’s solution is limited only to Windows 10 devices. Google Chrome on Android also lets you directly send webpages to your other devices, including Windows 10 PC, Mac, iPhone, and any other Android smartphone. Source: MSPU Tips: Here is how to use your Android smartphone as a means to send texts to your Windows 10 PC and other devices (MSPoweruser)
  19. Firefox Preview on Android now supports custom search engines Users of Mozilla new Firefox Preview browser for Android will soon be able to select a bigger variety of search engines and add custom search engines. Additionally, users will be able to remove any of the search engines provided by default, which is typical of the customisability we’ve come to expect from Mozilla over the years. The new search engines which have been added were picked due to a number of users requesting them; they include the tree-planting Ecosia, privacy-focused Startpage, Yahoo, Reddit, and YouTube. They join Google, Amazon, Bing, DuckDuckGo, Qwant, Twitter, and Wikipedia. If you're using the nightly version of Firefox Preview, choosing the new search engines is easy, just head to Settings > Search > Add search engine, from here you can select one of the pre-defined search engines or add your own. If you remove any of the default providers, they’ll be moved into this sub-menu. According to Sören Hentzschel who spotted the feature, users should receive the custom search feature in the upcoming Firefox Preview 3.1 update although it’s unclear when this update is planned for. Source: Firefox Preview on Android now supports custom search engines (Neowin)
  20. EFFECTIVE IMMEDIATELY — Google will pay $1.5 million for the most severe Android exploits Big bump coincides with investments Google has poured into securing its Pixel phone. Enlarge New Line Cinema Google will pay up to $1.5 million for the most severe hacks of its Pixel line of Android phones, a more than seven-fold increase over the previous top Android reward, the company said. Effective immediately, Google will pay $1 million for a “full chain remote code execution exploit with persistence which compromises the Titan M secure element on Pixel devices,” the company said in a post published on Thursday. The company will also pay $500,000 for exploits that exfiltrate data out of a Pixel or bypass its lock screen. Google will offer a 50 percent bonus to any of its rewards if the exploit works on specific developer preview versions of Android. That means a critical Titan M hack on a developer preview could fetch $1.5 million, and a data exfiltration or lockcscreen bypass on a developer preview could earn $750,000, and so on. Previously, rewards for the most severe Android exploits topped out at $200,000 if they involved the trusted execution environment—an independent OS within Android for handling payments, multi-factor authentication, and other sensitive functions—and $150,000 if they involved compromise only on the Android kernel. Putting Titan M to the test The big reward bump coincides with the investments Google has poured into securing the Pixel. The Titan M is a Google-designed chip that’s physically segregated from the main chipset of the device. In many respects, it’s analogous to the Secure Enclave in iPhones or the TrustZone in devices running an Arm processor. The Titan M is a mobile version of the Titan chip Google introduced in 2017. The Titan M carries out four core functions, including: Storing the last known safe version of Android to ensure hackers can’t cause the bootloader—which is the program that validates and loads Android when the phone turns on—to call a malicious or out-of-date version Verifying the lock screen passcode or pattern, limiting the number of unsuccessful login attempts that can be made, and securing the device’s disk encryption key Storing private keys and securing sensitive operations of third-party apps, such as those used to make payments Preventing changes to the firmware unless a passcode or pattern is entered Titan M was first introduced in 2018 with the roll out of the Pixel 3. It’s also in the recently released Pixel 3a, and will also be included in the just-released Pixel 4. Pixel 2 models relied on a less robust dedicated tamper-resistant hardware security module. In-the-wild exploits disclosed last month were able to remotely execute malicious code on an array of Android phones, including the Pixel 1, Pixel 1 XL, Pixel 2, and Pixel 2 XL, but not the Pixel 3. The Titan M wasn't responsible for stopping that attack, however. Instead, the reason was that the Pixel 3 and 3a received Linux patches that the vulnerable Pixels had not. In the four years since the Android Security Rewards Program was introduced, it has paid out more than $4 million from more than 1,800 reports. More than $1.5 million of that came in the past 12 months. The top reward this year was $161,337, which was paid to Guang Gong of Qihoo 360 Technology’s Alpha Lab for a one-click remote code execution exploit chain on a Pixel 3. (Gong’s exploit received an additional $40,000 from the Chrome Rewards Program.) The new rewards come almost three months after third-party exploit broker Zerodium started paying $2.5 million for zero-day attacks compromising Android, a 25-percent premium over comparable exploits for iOS. As tempting as it is to contrast the Zerodium’s top Android payouts to those from Google, don’t. The talent and amount of work required to develop a weaponized exploit for Zerodium are considerably higher than what Google demands, making for an apples-to-oranges comparison. Source: Google will pay $1.5 million for the most severe Android exploits (Ars Technica)
  21. android giveaway

    Home Workouts Gym Pro (No ad) | ANDROID

    All exercise guides by video animation 3D (It is easy to understand) Home Workouts No equipment Pro provides daily workout routines for all your main muscle groups. In just a few minutes each day, you can build muscle and exercise at home without having to go to the gym. No equipment or coach needed, all exercises can be done only with your body weight. This application includes exercises for the abs, chest, legs, arm as well as body training. All exercises are designed by exeperts. No need equipment, so no need to go to the gym. Although it only takes a few minutes each day, it can effectively tone your muscles and get six pack abs at home. Stick with our home workout, and you will notice a change in your body in just a few short weeks PRICE: $1.49 FREE FOR LIMITED TIME SOURCE: https://www.paidapps-free.com/2019/11/home-workouts-gym-pro-no-ad LINK ON PLAYSTORE : https://play.google.com/store/apps/details?id=fitness.workouts.home.workoutspro&hl=en
  22. Google & Samsung fix Android spying flaw. Other makers may still be vulnerable Camera and mic could be controlled by any app, no permission required. Enlarge Aurich Lawson / Getty Until recently, weaknesses in Android camera apps from Google and Samsung made it possible for rogue apps to record video and audio and take images and then upload them to an attacker-controlled server—without any permissions to do so. Camera apps from other manufacturers may still be susceptible. The weakness, which was discovered by researchers from security firm Checkmarx, represented a potential privacy risk to high-value targets, such as those preyed upon by nation-sponsored spies. Google carefully designed its Android operating system to bar apps from accessing cameras and microphones without explicit permission from end users. An investigation published Tuesday showed it was trivial to bypass those restrictions. The investigation found that an app needed no permissions at all to cause the camera to shoot pictures and record video and audio. To upload the images and video—or any other image and video stored on the phone—to an attacker-controlled server, an app needed only permission to access storage, which is among one of the most commonly given usage rights. The weakness, which is tracked as CVE-2019-2234, also allowed would-be attackers to track the physical location of the device, assuming GPS data was embedded into images or videos. Google closed the eavesdropping hole in its Pixel line of devices with a camera update that became available in July. Checkmarx said Samsung has also fixed the vulnerability, although it wasn't clear when that happened. Checkmarx said Google has indicated that Android phones from other manufacturers may also be vulnerable. The specific makers and models haven't been disclosed. "The ability for an application to retrieve input from the camera, microphone, and GPS location is considered highly invasive by Google themselves," Checkmarx Director of Security Research Erez Yalon wrote in Tuesday's analysis. "As a result, AOSP created a specific set of permissions that an application must request from the user." To demonstrate the risk, Checkmarx developed a proof-of-concept rogue app that exploited the weakness. It masqueraded as a simple weather app. Hidden inside were functions that could: Take pictures and record videos, even when the phone was locked, the screen was off, or the app was closed Pull GPS data embedded into any photo or video stored on the phone Eavesdrop and record two-way phone conversations and simultaneously record video or take images Silence the camera shutter to make the spying harder to detect Transfer any photo or video stored on the phone to an attacker-controlled server List and download any JPG image or MP4 video stored on the phone's SD card An attack wouldn't be completely surreptitious. The screen of an exploited device would display the camera as it recorded video or shot an image. That would tip off anyone who was looking at the handset at the time the attack was being carried out. Still, the attack would be able to capture video, sound, and images at times when a phone display was out of eyesight, such as when the device was placed screen down. The app was able to use the proximity sensor to determine when the device is face down. Checkmarx's PoC app was also able to use a phone's proximity sensor to detect when it was held to a target's ear, as often happens during phone calls. The app was able to record both sides of the conversation. It could also record video or take images, a useful capability in the event the back of the phone was facing a whiteboard or something else of interest to an attacker. Checkmarx's report includes a video demonstrating the capabilities of the PoC app. In a statement, Google officials wrote: "We appreciate Checkmarx bringing this to our attention and working with Google and Android partners to coordinate disclosure. The issue was addressed on impacted Google devices via a Play Store update to the Google Camera Application in July 2019. A patch has also been made available to all partners." Samsung officials wrote: "Since being notified of this issue by Google, we have subsequently released patches to address all Samsung device models that may be affected. We value our partnership with the Android team that allowed us to identify and address this matter directly." The statement didn't say when Samsung released the fix or how Samsung customers can check if the patch has been installed. Checkmarx said Google has privately indicated that other makers of Android phones besides Samsung may also be vulnerable. Google's statement didn't directly confirm this or say if any other manufacturers have installed an update. In an email, Checkmarx's Yalon said it wasn't clear why apps could access the camera without the user providing permission. He speculated that the weakness may be the result of Google making the camera work with the voice-activated Google Assistant and other manufacturers following suit. Users of Pixel phones can confirm they aren't vulnerable by accessing Apps and Notifications from the settings menu, choosing Camera > Advanced > and App details. The screen should show that the app has been updated since July (and ideally much more recently than that). Checking if other Android phones are susceptible will be difficult for most users. Those who are more technically skilled can run the following command: $ adb shell am start-activity -n com.google.android.GoogleCamera/com.android.camera.CameraActivity --ez extra_turn_screen_on true -a android.media.action.VIDEO_CAMERA --ez android.intent.extra.USE_FRONT_CAMERA true The above command will force the phone to take video. The following command will force the phone to take a photo: $ adb shell am start-activity -n com.google.android.GoogleCamera/com.android.camera.CameraActivity --ez extra_turn_screen_on true -a android.media.action.STILL_IMAGE_CAMERA - -ez android.intent.extra.USE_FRONT_CAMERA true --ei android.intent.extra.TIMER_DURATION_SECONDS 3 The skill and luck required to make the attack work reliably and without detection are high enough that this type of exploit isn't likely to be used against the vast majority of Android users. Still, the ease of sneaking malicious apps into the Google Play store suggests it wouldn't be hard for a determined and sophisticated attacker to pull off something like this. No wonder phones and other electronics are barred from SCIFs and other sensitive environments. Source: Google & Samsung fix Android spying flaw. Other makers may still be vulnerable (Ars Technica)
  23. Google outlines plans for mainline Linux kernel support in Android Google wants less forking, more modularization for Android's Linux kernel. First image of article image gallery. Please visit the source link to see all images. It seems like Google is working hard to update and upstream the Linux kernel that sits at the heart of every Android phone. The company was a big participant in this year's Linux Plumbers Conference, a yearly meeting of the top Linux developers, and Google spent a lot of time talking about getting Android to work with a generic Linux kernel instead of the highly-customized version it uses now. It even showed an Android phone running a mainline Linux kernel. But first, some background on Android's current kernel mess.Currently, three major forks happen in between the "mainline" Linux kernel and a shipping Android device (note that "mainline" here has no relation to Google's own "Project Mainline"). First, Google takes the an LTS (Long Term Support) Linux kernel and turns it into the "Android Common kernel"—the Linux kernel with all the Android OS-specific patches applied. Android Common is shipped to the SoC vendor (usually Qualcomm) where it gets its first round of hardware-specific additions, first focusing on a particular model of SoC. This "SoC Kernel" then gets sent to a device manufacturer for even more hardware-specific code that supports every other piece of hardware, like the display, camera, speakers, usb ports, and any extra hardware. This is the "Device Kernel," and it's what actually ships on a device. This is an extremely long journey that results in every device shipping millions of lines of out-of-tree kernel code. Every shipping device kernel is different and device specific—basically no device kernel from one phone will work on another phone. The mainline kernel version for a device is locked in at the beginning of an SoC's initial development, so it's typical for a brand-new device to ship with a Linux kernel that is two years old. Even Google's latest and, uh, greatest device, the Pixel 4, shipped in October 2019 with Linux kernel 4.14, an LTS release from November 2017. It will be stuck on kernel 4.14 forever, too. Android devices do not get kernel updates, probably thanks to the incredible amount of work needed to produce just a single device kernel, and the chain of companies that would need to cooperate to do it. Thanks to kernel updates never happening, this means every new release of Android usually has to support the last three years of LTS kernel releases (the minimum for Android 10 is 4.9, a 2016 release). Google's commitments to support older versions of Android with security patches means the company is still supporting kernel 3.18, which is five years old now. Google's band-aid solution for this so far has been to team up with the Linux community and support mainline Linux LTS releases for longer, and they're now up to six years of support. Last year, at Linux Plumbers Conference 2018, Google announced its initial investigation into bringing the Android kernel closer to mainline Linux. This year it shared a bit more detail on its progress so far, but it's definitely still a work in progress. "Today, we don't know what it takes to be added to the kernel to run on a [specific] Android device," Android Kernel Team lead Sandeep Patil told the group at LPC 2019. "We know what it takes to run Android but not necessarily on any given hardware. So our goal is to basically find all of that out, then upstream it and try to be as close to mainline as possible." Google says that "compared to [Linux] LTS (4.14.0), the Android common kernel has 355 changes, 32,266 insertions, and 1,546 deletions (as of February 2018)." Progress is being made here every year, but keep in mind there are still two more forks after this. Google While there is still work to be done for getting the wider Android ecosystem and myriad device configurations on board, for specific models of device, things seem to be progressing well. Tom Gall, the director of the Linaro Consumer Group, showed off a Xiaomi Poco F1 actually running the mainline Linux kernel under the usual Android OS. Gall told the audience "There are major, major props to be given to the Google Kernel Team in particular for getting their code upstream so that we can boot devices with a mainline kernel." Along with the plan to upstream as much kernel code as possible, Google is also looking to replicate its earlier work at modularizing Android, Project Treble. Just as Treble created a stable interface between the Android OS and the device HALs (Hardware Abstraction Layers), Google's proposal for bringing Android closer to mainline Linux (How is there not a silly "project" name for this yet?) involves stabilizing Linux's in-kernel ABI and having a stable interface for the Linux kernel and hardware vendors to write to. Google wants to decouple the Linux kernel from its hardware support. The Linux community has been against the idea of a stable interface for some time, with the suggestion that if you want the ability to quickly update a kernel, open source your drivers and get them in the main kernel tree, where any changes will be taken care of for you. Open sourcing drivers is an absolute deal breaker for many hardware companies, though, and no amount of advocacy or product degradation is going to change that. The fact that Google is stuck supporting five-year-old versions of Linux shows this model isn't working. Enlarge / Instead of a bunch of forks, Google imagines the new kernel as a series of modules. Matthias Männich Matthias Männich, a senior software engineer at Google, displayed a diagram labeled "Android Next Generation" that showed what this proposed kernel architecture would look like. Google would ship a "Generic Kernel Image (GKI)" along with several "GKI Modules" that would expose this stable API/ABI in the kernel. The hardware-specific drivers (probably closed source drivers) would be loaded as kernel modules. So instead of forks on top of forks, everything gets modularized into additive packages. For now, Google is only proposing that the in-kernel ABI be stable for a single LTS version. So this wouldn't allow devices to upgrade from one version of the Linux kernel to another—it would just allow for a single generalized kernel image to work across multiple devices, instead of the device-specific kernel forks we have today. It would definitely allow for easier security updates, and hopefully it would get new LTS releases to market faster. We would be premature if we said this is a change that is definitely coming to Android and the Linux kernel. There are still tons of problems to solve (both technically and politically, I would imagine), and some of these talks were more like public brainstorming sessions between the Google presenters and the Linux engineers (many of which were also Googlers!) in the audience. This is the second year in a row Google has showed up to LPC and pitched the idea of using the mainline Linux kernel in Android, though, and with Android being of the biggest Linux sort-of-distros on Earth, it makes sense for everyone to work together, right? "We have miles to go, and we know that, but we've come along from where we started," Patil told the crowd. "Last year, I talked it into existence. This time, we actually have problems to discuss." Listing image by Eric Adeleye / Flickr Source: Google outlines plans for mainline Linux kernel support in Android (Ars Technica) (To view the article's image gallery, please visit the above link)
  24. Chrome for Android has just solved one of the web's most irritating problems Browser notifications just got less bothersome (Image credit: Shutterstock) Google has added a new experimental option to Chrome for Android, which helps make alerts about site notifications less intrusive. The browser already has some options for customizing how these alerts appear, but the new setting aims (called 'Quieter notification permission prompts') is new for anyone using Chrome Canary on their phone or tablet. This setting is added to the existing 'Enabled', 'Enabled (force heads-up notifications)' and 'Enabled (force mini-infobars)' options. You can choose the setting you would like to use by visiting chrome://flags in Chrome, and then searching for 'Quieter notification permission prompts'. As Techdows reports, the new option can be found in Chrome Canary 80.0.3969.0 and newer, and as the name would suggest, 'Force quiet notifications' is far less intrusive than the other options. Quieten things down With 'Force heads-up notifications' selected, you'll be shown an aggressive popup informing you that notifications are available for a site, and giving you the option of blocking or allowing them. Select 'Force mini-infobars', and instead you'll see a small mini-message at the bottom of the screen. You can tap this to change settings, or just ignore it. With the new 'Force quiet notifications' option enabled you will instead see a soft notification in Android itself which you can deal with or ignore as you see fit. Source: Chrome for Android has just solved one of the web's most irritating problems (TechRadar)
  25. Microsoft is killing off its Cortana mobile apps everywhere except the U.S. next year If you're a fan of Microsoft's Cortana virtual assistant and you live outside of the U.S., you're in for some bad news, although that should frankly be no surprise. The company is ending support for the Cortana mobile app on iOS and Android as of January 31, as noted in a support document published this week. The support document is from the UK, as Microsoft isn't killing the app if you're in the United States. Indeed, the page also notes that Cortana is being removed from Microsoft Launcher on Android, something that was previously reported earlier this month, and that news is also exclusive to those outside of the U.S. Instead, Microsoft's strategy is to integrate its digital assistant into its various Microsoft 365 apps, such as Office, To Do, and so on. The Redmond firm was clear that it's not actually killing off Cortana, but only the mobile apps and the integration with Microsoft Launcher. It's unclear why the apps will continue to be supported in the U.S., so it's entirely possible that those will be removed at a later date as well. Source: Microsoft is killing off its Cortana mobile apps everywhere except the U.S. next year (Neowin)
  • Create New...