» Unlabelled » Moronic Monday (Dec 05 2016) - Your weekly questions thread!

Moronic Monday (Dec 05 2016) - Your weekly questions thread!

Monday 5 December 2016
Belum ada komentar

Moronic Monday (Dec 05 2016) - Your weekly questions thread!

Moronic Monday (Dec 05 2016) - Your weekly questions thread!

Posted: 05 Dec 2016 03:09 AM PST

Note 1. Join us at /r/MoronicMondayAndroid, a sub serving as a repository for our retired weekly threads. Just pick any thread and Ctrl-F your way to wisdom!

Note 2. Join our Discord, IRC, and Telegram chat-rooms! Please see our wiki for instructions.

submitted by /u/AutoModerator
[link] [comments]

7.1.1 Full OTA Images are ready for Pixel, Pixel XL, Pixel C, Nexus 6P, Nexus 5X, Nexus 9, and Nexus Player

Posted: 05 Dec 2016 09:54 AM PST

Google Assistant now understands Hindi, but only in Allo

Posted: 05 Dec 2016 03:01 AM PST

Welcoming Android 7.1.1 Nougat

Posted: 05 Dec 2016 11:23 AM PST

Let your loved ones know you’re safe with our new personal safety app

Posted: 05 Dec 2016 05:30 AM PST

A sweet update to Nougat: Android 7.1.1

Posted: 05 Dec 2016 11:53 AM PST

December Updates now live!

Posted: 05 Dec 2016 09:42 AM PST

The slow, uninteresting death of Android tablets is unfolding, and it is no one's fault (opinion)

Posted: 05 Dec 2016 04:53 PM PST

Introducing Toolbox for Google Play Store, a Chrome extension from us that improves the Play Store

Posted: 05 Dec 2016 11:27 AM PST

Moto Z Might Be The First Phone To Support Both Daydream And Tango

Posted: 05 Dec 2016 10:04 AM PST

HTC M9 Nougat update released!

Posted: 05 Dec 2016 03:38 PM PST

Android versions breakdown - December 2016

Posted: 05 Dec 2016 12:11 PM PST

Verizon Says Pixel Updates Arrive Today as Build NMF26O

Posted: 05 Dec 2016 08:00 AM PST

Allo now understands brazilian portuguese. New brazilian stickers as well.

Posted: 05 Dec 2016 10:32 AM PST

Android Nougat will begin rolling out to the unlocked #HTCOneM9 starting late this evening. Carrier variants to follow early next year.

Posted: 05 Dec 2016 03:31 PM PST

Android Security Bulletin - December 2016

Posted: 05 Dec 2016 09:59 AM PST

Xiaomi Mi 5s fingerprint sensor, the worst i have used.

Posted: 05 Dec 2016 03:40 AM PST

I got a Mi 5s three weeks ago, a well built device, packed with high end devices specs: CPU SD821, Camera Sensor Sony IMX378, 4GRam, 128GB of storage.

BUT somehow i didn't find any review (blog/youtube) talking about the fingerprint sensor issue.

I used many other devices with fingerprint sensor: Nexus 5X, 6P, GS7, OP3 and i must say Mi5s's one is the worst of the worst, it does not unlock most of the times.

I tried many "solutions" posted by some users on MIUI forums, but it is still inaccurate.

Here is a MIUI thread talking about this issue: http://en.miui.com/thread-397784-1-1.html

This is how this fingerprint sensor was marketed:

Ultrasonic fingerprint sensor

Xiaomi took a stage as the first mass manufacturer to mount in a fingerprint reader into a smartphone.

Seamlessly hidden in the body of the phone, a 3D sensor performs at a higher speed, is accurate and durable. The sensor rests under the 2.5D screen Gorilla Glass 4. Consequently, an additional on-screen slot is no longer required.

The biggest point of emphasis should be that the sensor is able to recognize a fingerprint even if a finger is wet or dirty.

I still hope this is a software issue.

Edit: A speed test between Mi5 and Mi5s FP on this video: https://www.youtube.com/watch?v=aqfLcwDtzIo Mi5s is the white one, thanks to /u/ag2f

submitted by /u/wanam
[link] [comments]

Xiaomi Redmi Note 3 (kenzo) gets first CM14.1 official nightly

Posted: 05 Dec 2016 10:46 AM PST

Cyanogenmod 14.1 Official Nightly released for Moto X 2nd Generation

Posted: 05 Dec 2016 08:49 AM PST

CM14.1 official nightlies for Xiaomi Mi Max

Posted: 05 Dec 2016 11:45 AM PST

CM14.1 official nightlies for Galaxy S3 d2vzw

Posted: 05 Dec 2016 04:33 AM PST

Huawei Mate 9 review

Posted: 05 Dec 2016 01:20 PM PST

Sony's best midrange device is on sale, $230 for the next 6 hours.

Posted: 05 Dec 2016 02:58 PM PST

A noobs guide to installing an OTA via ADB on a Mac

Posted: 05 Dec 2016 07:05 PM PST

Im new to android so I have zero experience installing updates manually or ADB or any of that. I'm also impatient and did not want to wait for the OTA to hit my phone. I did some googling to figure out how to go about manually applying the OTA and quickly became confused, mainly because most of the instructions are windows-centric. After finally figuring it out, I thought I would share my guide here in case anyone else is running into the same problem!

DISCLAIMER: If you fuckup your phone, I take zero responsibility. Why are you taking advice from a noob?

Prepare

  1. Download the OTA here. Make sure to pick the correct model (Pixel vs Pixel XL) and software (7.1.1)

  2. Verify your download by comparing the last portion of the filename of the OTA to first 8 digits of the checksum (Pixel 7.1.1: 3e7c4b66, Pixel XL: 54bb505e)

  3. Turn on developer options on your phone by going to Settings>About>Software Information>More and tapping "Build Number" seven times

  4. Open developer options and enable USB Debugging

  5. Plug in your phone

Install ADB / Fastboot

  1. Install Android Studio (Download here)

  2. Open Android Studio and follow the prompts to install

  3. Locate the platform tools folder (keep this open for the next few steps) by opening finder and browsing to /Users/<your username>Library/Android/sdk

Start Using ADB Fastboot

  1. Open up terminal and type in: cd followed by a space then drag the platform-tools folder into the Terminal window. Terminal should then show:

    $ cd /Users/YOURNAME/Library/Android/sdk/platform-tools

    1. Test adb is working by typing in terminal:

    ./adb devices

  2. If its working, you should see your phone and its serial number.

  3. Find the OTA you downloaded. To make the next step easier, rename it ota_file.zip.

  4. Move the OTA file to the platforms_tools folder

Install That Mofo

  1. Start up recovery mode by typing into terminal:

    ./adb reboot recovery

  2. Your phone should restart and you will see an android logo with a red exclamation.

  3. Hold Power and press Volume Up once.

  4. A menu will appear. Use the volume keys to highlight Apply Update from ADB, then use the power key to select it.

  5. Back in terminal, run the command ./adb sideload ota_file.zip

  6. Wait

  7. Once it is done (it will take a few minutes, dont worry) it will give you the option to Reboot the system now. Select it by pressing the power key.

  8. BAM!

  9. Bonus step: once up and running, disable USB debugging

submitted by /u/PM_ME_YOUR_TRADRACK
[link] [comments]

PSA: Android Pay and Multi User Accounts

Posted: 05 Dec 2016 02:13 AM PST

Hi guys,

Just a little something I found on my Pixel XL over the weekend which may save some of you some troubleshooting and headaches.

I upgraded from an iPhone 5S and Nexus 5X to the Pixel XL so I could combine my two user accounts (work and personal) on to one massive 128GB device. I migrated over my Android Pay cards from my personal account and all seemed to be working fine.

However, whenever I tried to use Android Pay I would receive the low pitched 'error' beeps, and a string of different messages on the various terminals I tried tapping on. "Card not supported, card not valid, contactless not available at this time...", you name it.

I had my bank replace my card. Still the same. I dug out the 5X and hooked up the new bank card to Android Pay, and it worked fine. What the hell? I tested the NFC chip on the Pixel XL with Android Beam and, yep, that was working fine.

So, I rang the carrier to ask if they could in someway have disabled Android Pay on the carrier locked device. I assumed this was impossible, and they confirmed that I was right. The NFC was out of their control to lock down on the Pixel.

I tried everything I could think of. Reactivated the card a bunch of times, tried other different cards I knew would work with Android Pay, rang the bank again...

It turns out that if you have a Google Apps for Education / Work whatever account linked on your phone which does not have Android Pay enabled by your Administrators, EVEN IF IT IS A SEPARATE MULTI USER ACCOUNT, Android Pay will NOT work, and will NOT tell you why.

Only through a bunch of testing did I realise this. This was even when Android Pay was uninstalled for the Google Apps for Edu user account.

Removing the multi user account and bundling it into my primary personal account as a secondary Google Account alleviated the issue straightaway though.

TLDR: A Google Apps account without Android Pay enabled on your phone by your domain admin added as another separated USER (not Google account) will break Android Pay for ALL USERS. Period!

Hopefully this might save some other users some hassle and from carrying two phones like I was!

Edit: Typo

submitted by /u/DavieMarshall
[link] [comments]
Thanks for reading my news about Moronic Monday (Dec 05 2016) - Your weekly questions thread! at my blog Custom Droid Rom if you want too share this article, please put the resource, and if you think this article is very usefully dont forget to bookmark this site with CTRL + D on your keyboard to web browser.

New and Hot Article's :

Arie-S-Ymbian-Android | Haries4game | AriesHp3

Note: only a member of this blog may post a comment.