• Breaking News

    [Android][timeline][#f39c12]

    Friday, February 23, 2018

    Home Unlabelled Android Help Hey /r/android! Oneplus broke camera2 api since the 7.0 update on OP3(T), rendering the phone unstable (as proved inside). Refuses to fix it, ignoring the all the complains. We need your help to show them how unacceptable this behavior is.

    Android Help Hey /r/android! Oneplus broke camera2 api since the 7.0 update on OP3(T), rendering the phone unstable (as proved inside). Refuses to fix it, ignoring the all the complains. We need your help to show them how unacceptable this behavior is.

    February 23, 2018

    Android Help Hey /r/android! Oneplus broke camera2 api since the 7.0 update on OP3(T), rendering the phone unstable (as proved inside). Refuses to fix it, ignoring the all the complains. We need your help to show them how unacceptable this behavior is.

    Hey /r/android! Oneplus broke camera2 api since the 7.0 update on OP3(T), rendering the phone unstable (as proved inside). Refuses to fix it, ignoring the all the complains. We need your help to show them how unacceptable this behavior is.

    Posted: 23 Feb 2018 09:13 AM PST

    Hey /r/android!

    We all praise the efforts from OEMs to keep our phones with the latest software. We love the updates for the new functionalities, increased stability or even for the sake of having a higher number buried on "about the phone" section. However it all goes to waste when companies, in this case, oneplus, break and/or limit functionalities which were working good, with a new update iteration.

    In this particular case, when the nougat update first started to roll out, people noted strange behaviors when using third party cameras (the ones that rely on camera2 API). Under some situations, the phones would hang for a long long time, crash, and display strange artifacts on the viewfinder. As it impacted heavily the phone camera usage, these issues were massively reported on oneplus forums, twitter and xda. (even by the creator of the known OpenCamera). Despite that, they got ignored, report after report, and still, to this day, almost a year later, there wasn't any official position on the issue

    On the other hand, using the stock camera app won't reveal any issues. Why? Because it's using a modded legacy API (with HAL3 for the front camera according to sultanxda) to make it work. (The fact that an OEM is still using this method in 2017/18 would deserve its own discussion, but I will leave as it is, since it's not particularly relevant for this topic). But, as you may ask, if the stock camera works seamlessly, why do we need to rely on 3rd party ones?

    Several reasons tbh:

    • Useless panorama mode
    • Lack of more advanced controls like intervalometer, exposure metering mode
    • Lack of manual video settings
    • Low quality 1080p time lapse mode
    • No sound with slow motion
    • (you tell me) /s

    For those who might have interest on the topic, I'll shed this additional information.

    • The camera will always crash during when pointed to bright scenes under some combinations of ISO and shutter speed.

    • The exif data (ISO and shutter speed) is incorrectly reported on dark scenes

    • Using full auto will allow higher than 799 ISO to be picked by the camera (despite the live stats of the app only read as 799). As soon as you force a manual control, the usable ISO range will be 100-799. Any higher than that and it is the same as 799.

    These itself result on a partially useless camera2 API implementation which, if it wasn't enough already, make the phone unstable for every user. All it takes is a camera app download from the play store.

    Detailed reports can be found HERE (XDA) HERE (ONEPLUS) and HERE (oneplus)

    Side note: currently Google camera port is not 100% stable on our device for the same freaking reason, as it relies solely on camera API.

    I don't like to free bash on companies, but this behavior is just unacceptable.
    Can't just understand how can oneplus have a device unstable for a year without the intention to fix that. I'm really trying to bring attention to this as it is not a minor bug at all.

    If this post leads to nowhere, at least I'm trying to inform people of the oneplus modus operandi. I still think their hardware is awesome (including my OP3T) but these decisions and the lacking support push me away from a future buy.
    Never settle you say?

    TL;DR: Oneplus broke the camera2api since nougat update. Refuses to fix it, there are no official answers, despite it being reported countless times. All OP3(T) on nougat or oreo are not stable. Will face reboots and crashes under some usage patterns due to this problem

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

    CORRECTION: Dark mode WILL NOT be added in Android 9

    Posted: 23 Feb 2018 03:38 PM PST

    Status: Assigned (Reopened) Hi folks, you may remember me from the last three releases where it looked like Dark Mode was being added. Unfortunately, this bug was closed prematurely due to a miscommunication with the team that handles AOSP issues.

    What we have added in a future Android release is a developer-facing setting (via Developer Options) to toggle the -night UI mode qualifier, which will make it easier for developers to create and test apps that implement night mode. This qualifier has been in the platform since Froyo (SDK 8) and globally modifiable via UiModeManager since Marshmallow (SDK 23); however, there was never an explicit toggle made available anywhere in Settings.

    If it's any consolation, we will also not be adding Hot Dog Mode (where all UI elements are yellow and red).

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

    Google needs to give the AirPods better competition

    Posted: 23 Feb 2018 11:23 AM PST

    Google's Former Head of Android Platform Security is now working on Fuchsia

    Posted: 23 Feb 2018 01:48 PM PST

    The Google Assistant is going global

    Posted: 23 Feb 2018 06:03 AM PST

    Google Testing Less Colorful Play Store Redesign With Bright Accents

    Posted: 23 Feb 2018 09:16 AM PST

    Meet Sony's first full screen smartphones: Xperia XZ2 and XZ2 Compact

    Posted: 23 Feb 2018 05:28 AM PST

    Announcing ARCore 1.0 and new updates to Google Lens

    Posted: 23 Feb 2018 08:03 AM PST

    OnePlus 6 previewed: iPhone X-like notch, dual camera and more

    Posted: 23 Feb 2018 09:44 AM PST

    HTC confirms US layoffs and will combine its smartphone and VR divisions

    Posted: 23 Feb 2018 10:01 AM PST

    CodeAurora Forum: Qualcomm's underrated developer contribution

    Posted: 23 Feb 2018 02:26 PM PST

    In light of the recent attempt by Broadcom to acquire Qualcomm, a discussion of what Qualcomm has done right and what we stand to lose is important.

    When you visit XDA-Developers to flash a custom ROM you are greeted with many different choices. The titles all have unique names and a plethora of tags in them. Some have the tag [AOSP], some [LOS], and some have the interesting tag [CAF]. You might not understand yet what these tags mean, and the developer community has not really written a great explanation for it. I will try to quickly clear up these concepts a bit in this thread.

    When Google releases a new Android version, they put their source codes on the AOSP remote here: https://android.googlesource.com/. These codes work on all Google's devices, and have a clean and organized history for every new Android "tag", a revision of Android. An example of such a tag is android-8.1.0_r14, the 14th stable version of Android 8.1. If you have one of Google's supported devices, you can follow their AOSP building instructions to compile these source codes for your device.

    LineageOS (previously CyanogenMod) takes these codes, and edits them to work on many more devices. They put their edited version on their GitHub page here: https://github.com/lineageos/. LOS is driven by community effort, and there is no monetary pressure for high quality testing (although bugs are still fixed quickly by the community).

    Chipset makers like Mediatek, Nvidia and Qualcomm want to implement their own hardware specific features into AOSP. They take AOSP like LineageOS does, and modify it to fit with their own chipset. These modified sources are what OEMs like Xiaomi receive when they buy the SoC from the chipset maker, in their case Mediatek for MT SoCs and Qualcomm for Snapdragon SoCs. AOSP is licensed in such a way that manufacturers can do this without having to release the source codes, and that means that only OEMs have access to the source codes for hardware specific features. One example of a hardware feature is the native audio post processor.

    Unlike Mediatek and Nvidia, however, Qualcomm releases their modified source codes on their own free will: https://source.codeaurora.org/quic/la/. There are instructions on how to build them for any phone with their SoC here: https://wiki.codeaurora.org/xwiki/bin/QAEP/. This is what XDA calls "CAF", because it is published on Qualcomm's CodeAurora Forum. Without this it would be a lot harder to build Android for other phones that are not supported by Google's AOSP.

    Developers know how essential having CAF is to building ROMs, and CAF is a big part of the reason why Snapdragon devices get so many more custom ROMs than, for example, Mediatek devices. If you feel like CAF is better optimized and feels smoother than AOSP or LOS custom ROMs, this is not a coincidence. Qualcomm has been experimenting with many CPU speed boosting algorithms that are all available to use in CAF.

    If Broadcom were to acquire Qualcomm, there is a high chance they would shut down the program as a waste of time. I find it saddening that many people are raising pitchforks when they hear the word 'Qualcomm' just because their performance does not match Apple's. They have arguably been the best chipset maker for the community, and open sourcing so much of their work should be praised more often.

    Note: I am not affiliated with Qualcomm

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

    [PSA] Unauthorized Data Skimming - DU Caller/Free Caller ID

    Posted: 23 Feb 2018 09:31 AM PST

    Greetings everyone! This is a general PSA to grow awareness of an adware which is collecting personal information. It acts like it is part of the typical android OS, however a quick look at the privacy statement shows the nefarious implications.

    What is it?

    This is a software called "DU Caller" which is using the Google Chrome app's cache to hide on victim's devices while collecting call information. It acts as a "Free Caller ID" program which appears with advertisements after phone calls. It does not show up as an installed application or in the app tray, as it isn't one. This program takes advantage of a vulnerability in the Google Chrome App to infect user's devices and presumably take contact information to add to their "Global Database of Over 2 Billion Numbers" (http://whosthat.mobi/). This program also prevents screenshots, likely to decrease the ability for users to report.

    I've seen several other users report this same problem throughout various forums, however, most couldn't find a way to resolve the problem without a full reformat.

    This is a vulnerability in both Android and Chrome, as their inter-connectivity is what is fostering the place for this infection to hide.

    I apologize that I do not have the steps to reproduce this problem. I'll include a list of all reported cases I can find. Many suggest it was an adware installed with other applications, however I strongly believe this to be false.

    What does it look like?

    Here's a picture: https://imgur.com/a/OVoqY

    It's a very sleek design with a blue background (t follows pretty closely to the material design guidelines). It pops up after every phonecall.

    How to Uninstall:

    The uninstallation process is very simple, actually. Just clear your Cache and Cookies in the Chrome App. The issue is that MANY people believe it is associated with an application and therefore spend hours uninstalling and deleting, finally resolving to a complete reformat (which sometimes doesn't even work if they have their Chrome data saved).

    Information:

    Privacy Policy - http://whosthat.mobi/static/whosthat/policy.txt

    This application claims "DU Caller will collect, process and retain personal information from You and any devices You may use in Your interaction with our Services. This information may include the following: geo-location, Your IP address, device ID or unique identifier, device manufacturer and type, device and hardware settings, ID for advertising, ad data, operating system, operator, IMSI, connection information, screen resolution, usage statistics, device log and event information, incoming and outgoing calls and messages, times and date of calls, duration of calls, version of the DU Caller Apps You use and other information based on Your interaction with our Services."

    Report!

    I've created a report with Google here: https://issuetracker.google.com/issues/73814527

     

    09-05-2016 | https://forums.androidcentral.com/general-help-how/720993-how-turn-off-whoscall-popup-dialog.html

    09-01-2017 | https://forums.androidcentral.com/oneplus-3-3t/830445-unknown-caller-id-spam-unable-uninstall.html

    09-06-2017 | https://forum.xda-developers.com/samsung-a-series/help/samsung-galaxy-a9-6-help-t3668659

    09-09-2017 | https://forum.xda-developers.com/galaxy-s8/help/samsung-galaxy-help-unknown-app-t3670422

    09-26-2017 | https://forums.androidcentral.com/samsung-galaxy-s8-and-s8-plus/835290-help-me-please-kill-free-caller-id.html

    10-10-2017 | https://www.reddit.com/r/techsupport/comments/75h4j2/can_anyone_help_me_id_and_remove_this_free_caller/

    02-07-2018 | https://productforums.google.com/forum/#!topic/play/KmQeAtFuUCg

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

    Samsung Galaxy Note8 long-term review

    Posted: 23 Feb 2018 04:58 PM PST

    New Galaxy S8 Oreo update now rolling out in more regions

    Posted: 23 Feb 2018 04:37 AM PST

    CarbonROM is now available on the Honor View 10 and other Project Treble-Compatible Devices

    Posted: 23 Feb 2018 07:36 AM PST

    Let's talk about Sony's new design

    Posted: 23 Feb 2018 03:44 PM PST

    Personally I don't really like it too much, the "brick" design of Sony's phones were a lot better IMO and the back curved glass/fingerprint sensor isn't really up my alley. But I also want to hear your thoughts and have a discussion on this new design.

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

    The most expensive car you can get with Android Auto: 2018 Lamborghini Aventador S

    Posted: 22 Feb 2018 10:16 PM PST

    @evleaks: Alcatel 1x, 3, and 3x

    Posted: 23 Feb 2018 01:47 PM PST

    Android Photography using Google Camera Mod ft. OnePlus 3T (See Album in post)

    Posted: 23 Feb 2018 06:41 AM PST

    Hello there my Android buddies and non-Android buddies alike!

    With the recent phones, we are seeing a plateau slowing being reached where in terms of everyday performance, it is hard to distinguish between the flagships and even the mid range phones. The primary difference is perhaps the camera and indeed it is a deciding point for many these days (alongside battery life).

    I recently went on a short vacation and even though I had my DSLR with me, I ended up using my phone to take almost 99% of the photos. It was just that much more convenient to snap and edit the photos then upload to the social media.

    Therefore, I have complied a small album of photos taken on my OnePlus 3T (not sponsored by anyone in any way XD) using the Google Camera Mod with the Nexus 6 Auto profile and HDR+ set to Medium. Some photos in the album are edited and they are under a separate section. Only Snapseed (a free photo editing app) was used to edit those. All photos were taken in jpg.

    Link to album: https://photos.app.goo.gl/dwbz3A5ShqX61LY03

    Even though OP3T did not have a good camera out of the box, I believe the Google Camera Mod managed to make the photos look great and perhaps I was lucky to have great weather in the UK and Paris.

    So enjoy the photos and let me know which feature for the upcoming flagships are you looking forward to that may just be the deciding factor?

    -Ali

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

    Galaxy S9 Spigen Cases are Live!

    Posted: 23 Feb 2018 09:29 PM PST

    ZTE Axon M Durability Test

    Posted: 23 Feb 2018 06:32 AM PST

    Moto G6 on Geekbench: Snapdragon 625, 3 GB RAM, Android 8.0 Oreo

    Posted: 22 Feb 2018 11:55 PM PST

    Google app v7.22 beta prepares page for purchases through Assistant, revised search widget editor, and more [APK Teardown]

    Posted: 23 Feb 2018 04:11 AM PST
    Read more
    at

    No comments:

    Post a Comment

    Fashion

    Beauty

    Travel