Hand-on quick review of the VIVO NEX

Android - Mon, 06/18/2018 - 20:37

I currently own a Samsung S7 Edge which I've enjoyed for a mere year before Samsung released both the S8 and S9. Having dropped my phone (before I got my case) that now has a cracked back glass, I've been looking to upgrade the S7 to the S8 S9. However, the recent releases of Chinese phones have gotten my attention (I live in China), in particular this VIVO NEX which I saw in person yesterday. Here are some of the sample shots that I took with the S7 edge (I'm not sure of how to post videos as I have footage of the front facing popup camera):

  • The NEX feels very solid and well built. It is a huge phone so it might feel a little hefty for small hands, but if you look at the picture it is a woman holding the NEX and she has no trouble operating it. Like most phones, it will require a case and front screen protector which is mandatory in China (I see people drop their phones at least once a day).

  • The volume control is on the right, which took some getting use to because most phones have it on the left.

  • The screen is absolutely gorgeous to look at. It is virtually the entire front face of the phone. This was what we should have been looking at for the Samsung S9 (not too bad) and Apple X (worst design I've ever seen). Why after a decade a company can only come up with a notched screen is beyond me. This is the future of mobile phones. The Amoled screen gets better every time I see it. With Apple adopting this technology as late as last year, there is no reason why we can't view gorgeously bright colours and deep blacks on any of our displays.

  • The bezels are better than anything I've seen, I'm not sure if I can still call them bezels. Borders may be a better word to describe them. I remembered my first impression seeing the S7 edge's screen and how beautiful it was compared to the super-thick bezels of past phones. It was like comparing modern jeans with flared pants from the 70s (do take a quick look at a vintage iphone 4s lol). The NEX however is truly a step into the future like I've never seen before. I have seen and used the Xiaomi Mix and Mix 2s, but they still have the camera on the front (and in an odd location). They're not truly bezel-less. The NEX is. There are no cameras, sensors, speakers or buttons that warrant the extra space for bezels. This is a border that is slightly more noticeable at the bottom of the NEX. It's a non-issue IMO and far less bothersome than staring at notches all day long.

  • Vivo claims that their speaker technology is unique on the NEX, and it is. There is a speaker at the bottom of the phone but the ear speaker is no where to be seen. Apparently this is behind the screen and it works quite well. The speakers while playing music are as loud as any other but I still have access to a 3.5mm audio jack for my cabled headphones and real speakers. If this was what made the bottom screen border slightly bigger then this is totally a non-issue.

  • The popup camera was what I was anticipating the most. It is super cool the way you press an onscreen button or app and it pops up. It isn't slow either, I guess it was as responsive as a popup flash on a DSLR camera like the Canon 7D. It felt solid though I didn't test the rigidity of it in case I might really break it. VIVO claims that the mechanism is just as reliable as any other self-closing mechanism on camera and projector lenses. I didn't feel like I missed the traditional spot for the front facing camera at all while enjoy the benefit of the full screen.

  • I was not able to test the on-screen fingerprint feature as the sample I used was probably the basic model (3898rmb). Is this feature worth almost $100 more? I'm not sure. I think the back fingerprint scanner does the job for most things like payments at the supermarket or restuarants. I do think it is a better alternative to the front fingerprint scanner on the button of my S7 edge and previous Samsung phones.

  • The OS and software were fluid and easy to use. I'm not all that big on skinning and custom ROMs and I have been using Samsung phones since the Galaxy SII. Having used my GF's phones, I have no issues with the software other than the onscreen keyboards which were a little smaller than I would like.

Is the VIVO NEX the hype that it claims to be? Absolutely.

However there are still a couple of things that holds me back on this phone:

  • Lack of expandable memory. I'm so used to having them on my Samsungs because I need more space for photos and videos. On my 128GB phone I can add another 128GB or 256GB of storage to play with. I can't get that with most phones like the NEX that doesn't have this.

  • No waterproofing capabilities. Perhaps this would be in the next version, but it really needs to be a standard on all phones. They are portable devices and are subjected to falls and elements from the weather.

Other than that, the NEX is a dream phone for gadget and technology lovers. I'm now waiting to see what the OPPO Find X has. They would be the second company to come out with a notch-free "bezel-less" screen design.

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

AutoLocation Geofences: two non-intersecting actually too far geolocations are active

Tasker: Total Automation for Android - Mon, 06/18/2018 - 20:20

Hi everyone,

I have a Note 8 with Android version 8.0.0. I'm new to android so I didn't make any changes on my stock rom (I don't know a thing about Android OS). I'm using Tasker for about a month and AutoLocation for a couple of days.

Today I faced with a strange issue with AutoLocation Geofences. I have two geofences with 9-10 km far from each other. One have 30 meters radius and other have 40 meters. I have enter and exit tasks and variables for both of the geofences separately (i.e home geofence profile makes %HomeGeofence=1 in its enter task and 0 in exit task, similar for work geofence and %WorkGeofence variable in another profile etc). But I saw that I have both %HomeGeofence and %WorkGeofence have values 1, I thought that it was a Tasker priority error or maximum tasks queue limit reached. But then I checked the geofence settings in AutoLocation app. Both home and work geofences shows the desired areas for my home and work, with correct radiuses. I also see my live location (blue dot) in my home area, not in the work area. But still both geofences shown as active, ie. names are green. I cannot think of a solution bu the I deleted the work profile and re-add the work geofence. Now everything seem to work like normal but it's just 2-3 hours and I'm still at home so not sure that I'll face the issue again or not.

I'm also using Llama so I turn the geofence monitor OFF in tasker after 5 min.s that I'm outside of all geofences (all geofence variables are 0). And turn it on as soon as Llama catches a known cell. But since I never quit from Work (this is what AutoLocation thinks) Geolocation monitor didn't turn off while I'm coming home today.

For it might be asked, I always keep my location at battery saving mode, mobile data, wifi and BT are always on. I also have the improve location accuracy settings "wifi scanning" and "BT scanning" on.

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

Valmynd: (Easier?) Dynamic ActionBar Menus for Fragments

Developing Android Apps - Mon, 06/18/2018 - 19:52

Last night I was really disappointed with my options for giving each Fragment in my Single Activity app it's own ActionBar Menu, so I hacked up this as my first Android Library.

Supports "inflating" menu items in a Fragment from a custom xml file, in code, or from a remote server as long as a MenuState object is provided to the MenuProvider.setMenuState.

Originally designed for use with AAC ViewModel and Navigation, though it should work independently of those.

Disclaimer: I have about half an idea what I'm doing. Everything is still pretty basic. Comments, suggestions, and contributions are all greatly welcome.

submitted by /u/cannabudha92
[link] [comments]
Categories: Android, Linux

Honor View 10 US updated with EIS

Android - Mon, 06/18/2018 - 19:45

My Honor View 10 in the US finally got the may update that included the may security pass, some AR shooting modes, and finally EIS here is a link of me walking with it on.

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

On the hunt: Android Developer

Developing Android Apps - Mon, 06/18/2018 - 18:04

Company: MySplit

Job: Android App Developer - MySplit

Location: Orange County, CA

Allows remote: prefer in person but accept remote

Visa: No

Description: MySplit is a new type of group expense consolidation application that will completely change how groups of friend and family pay for group expenses, split group expenses, and transfer money between each other instantly. I, Omar Jandali - Founder, am looking for an Android developer to help and build the Android App version of MySplit, while I build the Web platform. Highly prefer a developer living or based out of Socal from LA to San Diego.

submitted by /u/itsmeomarj
[link] [comments]
Categories: Android, Linux

Big project question

Developing Android Apps - Mon, 06/18/2018 - 16:48

Hey guys, I've got a question about how to navigate and understand a big andorid project.

So, long story short, couple of weeks ago I managed to get a decent job in a bank as junior android dev. The project have been build by a team of 5 engineers, over a period of 2 years. There are a bunch of modules (like 10 at least), hundreds of folders separated by features, screens, etc. The quality of the project architecture by itself is really great and impressive, no issues here. (MVP, clean architecture, [view, presenter, interactor, repository], dagger, rx, kotlin etc]

Well, it's been overwhelmingly complicated for me to build some sort of a mental map/image of this project. Even a trivial task take me tremendous amount of time and effort to do. Like add some arguments to constructor, then pass some data as a parameter to these methods using dagger and dependency graph.

So, the question is simple: How one can familiarize himself with a huge code base? How to build a mental picture, or even

understand what the general approach and architecture is? Or how to navigate huge code bases/projects?

Maybe there are some great approaches using android studio? Or other techniques/tips/trics?

Thanks a lot

submitted by /u/aandreyev
[link] [comments]
Categories: Android, Linux

Building HTML5 game to Android. Where to start?

Developing Android Apps - Mon, 06/18/2018 - 16:00

Hey guys!

I have been working on a small HTML5 game for couple months now. At this point the game is almost finish. Right now I want to build the game for other platforms and thought I could start with Android. I have some experience with Java, but not really at master level. I'm kinda confused how to start. I have read about hybrid apps with help of Cordova and it doesn't really look that hard but still not sure should I focus on that or instead go for Native. Or something else?

I will be really thankful if someone recommend me PDF or video about that topic.

submitted by /u/KungFuFlames
[link] [comments]
Categories: Android, Linux

I have android Messages for web with dark theme!

Android - Mon, 06/18/2018 - 15:44

Proof!!!. I installed the latest APK from apkmirrior.

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

[HELP] Menu scene elements are hard to tap

Tasker: Total Automation for Android - Mon, 06/18/2018 - 15:39

I have a little budget project which is constantly evolving. The last thing I did is I added a POI search for my cash popup task. l chose menu element in a scene for this, and populated the menu with an array (via Autolocation).

It all seems to work fine but the texts are really hard to tap. There is only a little area of every element which is tappable and I can't find the reason why.

Link to the scene: Google Drive

Link to the video:

Cab anyone guess what could be the problem?

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

With Kotlin settled in, why is Google publishing new code without nullability annotations?

Developing Android Apps - Mon, 06/18/2018 - 15:30

As we probably all know, use of @NonNull and @Nullable in Java is picked up by Kotlin's linter, which is awesome and handy.

These annotations in first-party code are important because it's easier for us developers to write Android apps that don't crash if the code we rely on works in a predictable manner.

I was using WorkManager today - which is in Alpha and possibly explains the whole thing - and noticed that these annotations are used inconsistently.

For example, here's one method in WorkManagerImpl:

@Override @WorkerThread public @Nullable WorkStatus getStatusByIdSync(@NonNull UUID id) {

and here's the one right above it

@Override public LiveData<WorkStatus> getStatusById(@NonNull UUID id) {

there is no way to know if the returned LiveData can be null

"but that's an internal class, you'll be using the public api." Fair enough, but WorkManager doesn't have any nullability annotations on its method return types at all.

Is this just because it's in alpha? Shouldn't there be CI checks for this kind of thing, or at least code conventions that get called out in code reviews? Is there some other reason for what I'm seeing?

submitted by /u/Wispborne
[link] [comments]
Categories: Android, Linux

I am feeling pretty disillusioned about the state of Android and Tech in general..

Android - Mon, 06/18/2018 - 14:48

For awhile I have felt a growing sense of discomfort about information collection, targeted advertising, and the general use of my data for purposes I don't agree with. That all being said I feel powerless over any of it. This really drove home when I watched a documentary on Netflix (Terms and conditions may apply) that spelled out in better detail what is seemingly occurring now. What are you experiences on this?

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