9 ms·
Android Studio 3.2
- deleted 8y ago[deleted]
- dafrankenstein2 8y agowell can anyone clarify what's the difference/relation between intel haxm and microsoft hyper-v
- jontro 8y agoLooks like haxm has the best performance, however you might want to use hyper-v if you're running other hyper-v containers since it clashes... https://stackoverflow.com/questions/32226559/making-hyper-v-and-intel-haxm-to-co-exist https://stackoverflow.com/questions/32226559/making-hyper-v-...
- ivankolev 8y agoNewest windows versions allow running docker and the android emulator side by side,through windows container platform
- kristianp 8y agoDo you have a link to show how to do that? Sounds useful, but the only reference I've found to that is to do it from Visual Studio and using Xamarin C# and not 'native' Java.
- ivankolev 8y agoOnce you enable the container platform in windows, and enable the bios setting for virtualization, it should just work, when I get back to my home computer I will look the details
- ivankolev 8y agoAlright, so I just made a run of it and verified it all works. As you say, the tutorial from Microsoft is for VS[0], but it actually talks about the android emulator, which is the same thing that Android Studio uses, just make sure you update it to latest, atm it's 27.3.10 Admittedly, the startup time seems a bit longer than with HAXM, but otherwise the emulation is pretty responsive. [0]https://docs.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?pivots=windows https://docs.microsoft.com/en-us/xamarin/android/get-started...
- kristianp 8y agoHaxm doesn't use hyper-v, hence you must disable hyper-v to use haxm.
- WorldMaker 8y agoIntel's HAXM is a lightweight hypervisor (supervisor in charge of VM supervisors) that is so lightweight because it is primarily a thin wrapper around hardware support (which should seem unsurprising given Intel's direct involvement), bypassing the Operating System (for the most part). Microsoft's Hyper-V is the hypervisor platform built into modern versions of Windows and which shares/follows (for the most part) Microsoft's overall Platform APIs and Driver APIs, making for a better communication channel between Hyper-V and the usual Windows supervisors/kernels when hosting Windows virtual machines. (Similar to the integration services offered by other hypervisors like VirtualBox, with the "magic" that such services are easier because the OS and the hypervisor share very similar "languages" already.) Microsoft's Hyper-V is also the base component for other systems such as the Windows Container Platform, some of Windows 10's more optional enterprise sandboxing systems, etc.
- copperx 8y agoRyzen support at last!
- foobaw 8y agoDo the emulator and compiler still require SSDs and 16GB+ RAM to be usable? I love Android Studio but it used to always feel very heavy-weight.
- lgleason 8y ago16GB is the bare minimum, but with some thrashing. 32 to really be usable, especially when running emulators.
- copperx 8y agoWhy has this been downvoted? I like Android studio but you do need to have at least 32GB of RAM for it to feel snappy. 16GB gives you a very usable, but sometimes laggy experience.
- deleted 8y ago[deleted]
- dvh 8y agoI'm using almost daily Android studio on Celeron J3455 with 4GB ram on Ubuntu 16.04 64bit and it's usable. I mostly do WebView apps, it is also on some cheap SSD.
- aikah 8y ago> I'm using almost daily Android studio on Celeron J3455 with 4GB ram on Ubuntu 16.04 64bit and it's usable. I mostly do WebView apps, it is also on some cheap SSD. I don't think it's possible to run the emulator with more than 5 FPS with this kind of set up. Let alone the editor itself which frankly runs like crap on low end hardware. The irony is that eclipse was much much faster in constrained environments. It's like IntellJ spends its time indexing and when it's done it's doing some more indexing just for kicks.
- kllrnohj 8y agoMy AS + Emulator running together is sitting at 3GB RAM. Definitely doesn't need 16GB+
- TekMol 8y agoI try Android Studio for a bit every now and then. I have to say it's such a giant bloated thing that it really does not make me want to write native code. Fortunately, there is a lot of great stuff going on with Progressive Web Apps now. I hope that they will be the future. Developing for the browser is so much leaner.
- watty 8y agoDeveloping for the browser is leaner but it's the opposite for end-users. I hope PWAs are the future as well but native is still king for the time being.
- TekMol 8y agoAs a user, I totally prefer a web app over a native app. Man .. don't even get me started .. ok, here we go: I can use it instantly. I can remove it instantly. The sandboxing is much better. The privacy is much better. I can link to it from wherever I like. I can use it on all my devices. I can copy text and images. I can change the style (I often enlarge the font for example). It can not use my battery / camera / phone when it's closed. ... I feel like I can go on forever.
- kuschku 8y agoI open 2 web apps at the same time, and the phone crashes (all RAM exhausted). I open a web app, and it lags horribly for minutes before becoming even semi-usable. This is on a Nexus 5X, using stock Android. Web apps are a complete joke right now. Entirely useless. I always install native apps, if available — even if I know I’ll uninstall it 5 minutes later — because the alternative is entirely unusable on my device.
- TekMol 8y agoThat does not make sense. Web apps do not consume more resources then websites. And usually less then native apps. I never had them crash any phone.
- netcraft 8y agoIs android studio a rebranded intellij?
- stephenhuey 8y agoYes https://jaxenter.com/android-studio-dumps-eclipse-for-intellij-idea-106065.html https://jaxenter.com/android-studio-dumps-eclipse-for-intell...
- spiderfarmer 8y agoYes, they used Intellij IDEA community edition as the base and built on top of it.
- mkhalil 8y agoMost exciting feature: App Bundles! At last, users with an Galaxy S5 won't have to install the same APK as a Note S9. This will especially helpful to users in countries where data is expensive, phones are old, and storage is low. Also, I can see this ensuring users download through the app store, since app pirates (most of the time, injecting trojans into free programs), will have to upload many different APKs in order to "trick" users into installing their APK. The Energy Profiler is a nice addition, but I wish there was some incentive for apps to be energy efficient (even an app store "badge" would be better than nothing), since people will continue to just blame Android for the battery performance and not the apps. super-small-nit: It's Android Studio 3.2, but the installer's file name is android-studio-ide-181.5014246-mac.dmg. android-studio-3.2.dmg would of been just fine. I am guessing 181 is a build number, but as a user, I don't care about what build number it is.
- ivankolev 8y ago181 is actually 20(18)1st release, following the underlying IDEA version. They lag behind one version, IDEA now is 182 and 183 is in early release program(eap)
- jackameister 8y agoOne nice feature that's somewhat buried in the notes is that the linter can now warn against some Kotlin/Java interoperability problems. But you need to turn the new inspections on manually: https://developer.android.com/studio/releases/#lint https://developer.android.com/studio/releases/#lint
- dirtylowprofile 8y agoI have been using AS since the first beta came out and every release it is just getting worst and slow on 16GB RAM. While Xcode on the other hand 3-4 years ago it was liked developed by interns. But Xcode 9-10 has been very fast and less buggy on my 16GB. Developing for Android is not fun anymore for me. It is getting bloated.
- lokedhs 8y agoI have used IntelliJ IDEA since the early 2000's and used it for Android development since Android first came out. It used to be an amazing experience, and when the news came out that Google was going to switch to IDEA for their official tools instead of going with that Eclipse I was thrilled. Finally everybody was going to able to know just how fast and efficient Android development can be. How wrong I was. When Android Studio came out, it was incredible slow. Even today, after years of improvement to the developer experience it still isn't as efficient as plain IDEA was before Google created Android Studio. I actually lay most of the blame on Gradle, which became mandatory around the same time. I never thought that someone would create a buid tool I dislike more than Maven, but it seems they succeeded.
- russellbeattie 8y agoGradle is pure insanity. Take a JVM-based scripting language that no one uses, and base an entire build-tool around it - complete with a custom DSL - that is so slow it needs to be run in the background as a service to be even somewhat performant, and make sure that each new version somehow breaks older build scripts so that you're constantly being prompted to update, and then being prompted to fix whatever the update broke... It's honestly just pure, unadulterated, crap.
- jrs95 8y agoMaven is very unintuitive though, at least Gradle does a better job on the CLI interface. Hopefully we'll get better options on the JVM in the future.
- lokedhs 8y agoBut you need to edit the Gradle configuration files. Most people simply cargo-cult that, and while that works most of the time, it's incredibly non-intuitive to solve problems.
- jrs95 8y ago99% of the time this is just pasting one dependency line into a file, and a Gradle file reads more intuitively than a Maven pom file. IMO performance aside Maven really only excels in edge cases. Most projects would never see any advantages from using Maven instead.
- calferreira 8y agoIn my opinion this a very exciting release. Google is really pushing to make the platform better for everyone, users and developers. Android App Bundles, Integration with Hyper-V and support for AMD are very welcome. Just wish using Android Studio required less ram and CPU, but to be honest, IIRC developing with Java has always been a little demanding when it comes to machine resources.
- Alexendoo 8y agoThere is quite a large downside to app bundles, that is that it requires you (the developer) to hand over your app signing key to Google. The fact that updates from the play store are signed end to end is pretty great in my opinion, this doesn't apply so much if you give away your signing key. As far as I can tell it's not a technical reason why they ask for your key - bundletool [1] supports generating a set of signed APKs (.apks, APK set archive) in the same way the play store would from an app bundle. Android Studio's GUI could just as easily generate that to upload directly to the play store instead of an app bundle. This would net the same benefits to the end users and the same level of convenience to the developer, all whilst keeping your private keys private. [1] https://developer.android.com/studio/command-line/bundletool https://developer.android.com/studio/command-line/bundletool