Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
LG Unveils V20 Android Nougat Phone With 3.5mm Jack, Audiophile Smarts
- Thread starter MacRumors
- Start date
- Sort by reaction score
No fan boy here.. I develope for iOS and Android. I own an iPhone 6S Plus and a Huawei P9.
If they left Java behind and built their apps on a more advance language then they might achieve a better platform for companies like Samsung and Huawei who have awesome hardware and sleek looking devices.
Don't get me wrong, they've come a long way over the past 4 years but they are still years behind on a OS and software level.
Its all about what an individual values in a device for whatever it costs. If they're both the same price and offer similar features and performance, each person determines what they like more or what they like to look at more. The iPhone isn't always going to be the right choice for everyone.If you're going to pay as much for an Android phone as you would for an iPhone, why not just get an iPhone?
LG phone article on a site about Apple products. Let's get a Windows phone story while we are at it!
The LG phone and Android are direct competitors to iOS and the iPhone and has a direct correlation to what the readers of MacRumors are interested in. The site attracts a wide variety of readers with numerous interests and this is just one aspect of them.
Why would they leave Java behind? It's easy to program in, it has very wide adoption, plus a wealth of libraries doing almost anything you want. I'd much rather write code in Java than in Objective-C.
On top of this, if you really don't like Java - or have legacy C/C++ code - you can always use NDK. It doesn't cover all the Java APIs, but if you need anything there's always JNI.
This kind of unsubstantiated claim is hard to take seriously. As far as functionality goes, that's clearly not the case.
Anyone who says that an Android smartphone can take "studio quality recordings" without context cannot be taken seriously.
Fixed it for you.
That's how you make a superior audio for a phone, the DAC.
[doublepost=1473255358][/doublepost]
Cause another phone manafacturer can?? It's about the hardware, what's the beef with android ? Just curious
[doublepost=1473255358][/doublepost]
Cause another phone manafacturer can?? It's about the hardware, what's the beef with android ? Just curious
Here is the equivalent of the iPhone 6: http://www.theverge.com/circuitbreaker/2016/9/6/12798436/amazon-moto-g-play-prime-exclusive-unlocked
Why, can the iPhone microphone take "studio quality recordings"? I was under the impression that it's just a bog-standard mobile phone microphone, i.e. bottom-of-the-barrel, no connection whatsoever with quality.
take another look at that fingerprint reader home button and tell me with a straight face it's not a copy of iPhone. no sir.
The basis for my opinion is not down to the dislike of the language but as previously stated that Java is sluggish compared to let's say Swift. I understand that Java is an easy language to code in but that doesn't bolster its speed or fluidity in comparison.
I'm just making a clear case that if Android was at a better stand point with its OS then phones manufacturers would be in a better place. I'm sure this will come with time but as it stands to a certain degree it doesn't matter how much ram or how fast the processor speed they are all held back by the operating system.
You mean the one on the back? I can only assume that's sarcasm.
You're looking at the wrong phone perhaps? The V20 has an on-screen standard Android home button, the fingerprint reader is on the back and I doubt it works as a home button. It usually just unlocks the phone and perhaps has other functions - for example, the P9 fingerprint reader supports gestures, so it can be used to scroll down the notifications pane, or scroll photos etc.
I've been a Java developer for roughly 20 years. I use Android phones now (after years with Apple ones). I prefer developing in Java.
All that being said, Swift is absolutely, hands down, vastly better for UI development. I've used it, and I'm a convert. I personally still prefer Java under the covers, but for UI - and let's face it, that's a huge chunk of app code - Swift destroys it. I don't want to lose Java's vast libraries, but I wholeheartedly agree Swift (or something like it, because Apple will never move Swift to Android) would be a fantastic help to Android app development.
I don't know if there's any inherent advantage that Swift enjoys over Java. The first Google search hit reveals this, which would suggest that is not the case.
I literally have no idea what you mean by "held back by the operating system". Since Android is an actual multi-threading OS, vs basically the single-thread experience of iOS, this is a core difference with pluses and minuses. Today's Android phones, save perhaps for the extremely cheap ones, are usually fast enough to present a fluid OS interface and in-app experience.
As far as OS experience goes, I think Android's is far superior, given its app <-> app and app <-> OS interaction and filesystem exposure, both of which are severely hampered or non-existent on iOS.
I don't think it's faster in operation, but it - for me - provides a much faster development environment for UIs. Obviously, to each their own, but I'd like something a bit better than Android Studio (although that might be because I'm not a huge IntelliJ fan).
Agreed (which is why I'm not on iPhones anymore, despite the fact most of the rest of my family still is).
OP made a generic comment about studio quality. Nobody could make a studio quality recording with mics located in a smartphone no matter how good they claim they are. It's like claiming a smartphone camera can take DSLR quality pictures with a tiny sensor and lens. It's basic physics.
My comment was more about the fact Android is light years behind iOS for anyone who would attempt to actually record something. Android simply doesn't have the underlying architecture to support this. I could, for example, connect an external studio quality 24bit 96KHz ADC to my iPhone and record 16 channels of audio in real time. It's not hatred or a beef with Android, it's just a fact of life.
Anyone wanting to make "studio quality recordings" on mobile devices would use iOS.
[doublepost=1473258200][/doublepost]
This is so wrong I don't even know where to start.
iOS is a fully pre-emptive multi-threaded multi-tasking operating system. Where on Earth did you get the idea it's single-threaded? And you're calling out a developer above for something they say? Oh the irony.
Were you the person looking for file directory on Youtube and Netflix? Did you also submit a feature request for it?
So basically you state that the iPhone cannot make studio quality by itself, but if you plug in something to it, it could. I hope I understood you correctly?
And you bring as proof that iOS is suitable for this kind of operation a hypothetical that generates 262.4Mbytes a minute of audio data, on a device where at most you might have 100Gbytes of storage? Who'd do that?
[doublepost=1473258200][/doublepost]
Sheer nonsense. It's got a severely limited multi-tasking experience, and as a programmer, you have to jump through all sorts of OS hoops to get your stuff to run in the background.
There's a reason for this - the much-swooned-upon iOS smoothness requires basically near-full CPU allocation on the UI/main thread, and very little on the background tasks. Add the small batteries and thus the necessary super-aggressive optimisation, and you get an environment which is fundamentally incongruent with a modern multi-tasking OS.
No availability date or price? Clearly LG's only intention was to beat Apple to an announcement. This thing might not even be available for over a month. LG shouldn't be getting any publicity at all for this vaporware until people know when they can buy it and for how much.
No phone can make studio quality recordings by itself. But with iOS you have the option of doing so using external gear since the support for such hardware is built into iOS. Not so on Android, where today's flagships still have issues with things like audio latency.
As to your question "who'd do that"? Well, millions of people actually do that. iOS has a huge library of Apps for this type of work and incredible support from aftermarket accessory makers. It's not hypothetical when people are actually doing it.
So wait, now you're changing your tune? First you claimed iOS was single-threaded and now you're talking about multitasking? Do you retract your original post where you said iOS was single-threaded?
And I never use the analog headphone out of my rMBP. The only thing that goes in there is an optical audio cable. Headset/microphone go into the USB port. I still have an almost perfectly working iPod Touch. The only thing that doesn't work on it is the analog headphone out connector. Get's connected through USB to my car stereo.Not sure what you are saying
