I see people say that you should not use Android Studio as your only IDE. I have tried searching on Google to see if you can sign / publish via Android Studio but I'm having trouble finding the answer.
Is it possible to use only Android Studio to fully code and publish an app? What problems are there with Android Studio?
Well for starters android studio isn't even 1.0 yet. It is heavily in beta and not exactly stable yet.
Eclipse is often recommended because it has a ton of documentation. Most tutorials will talk about eclipse.
Sent from my Nexus 4 using XDA Premium 4 mobile app
ryan.dawkins said:
Well for starters android studio isn't even 1.0 yet. It is heavily in beta and not exactly stable yet.
Eclipse is often recommended because it has a ton of documentation. Most tutorials will talk about eclipse.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Right. But what are the actual issues with it? Just being in beta doesn't really say much. Gmail was in beta for almost a decade.
I use Android Studio since it's been released. For simple app development, what i use for, it's good enough. You can build signed APK's. However there are always some bugs, but stackowerflow always knows the solution. I had some problems when importing from eclipse, i recommend to open a new project and copy the sourcefiles for full compatibility. I think Android Studio is better than eclipse!
medwe27 said:
I use Android Studio since it's been released. For simple app development, what i use for, it's good enough. You can build signed APK's. However there are always some bugs, but stackowerflow always knows the solution. I had some problems when importing from eclipse, i recommend to open a new project and copy the sourcefiles for full compatibility. I think Android Studio is better than eclipse!
Click to expand...
Click to collapse
Thank you. What kind of bugs were there? I'm interested to know the limitations.
Good recommendation. I'll start a fresh project and copy in my java files.
Paul22000 said:
Thank you. What kind of bugs were there? I'm interested to know the limitations.
Good recommendation. I'll start a fresh project and copy in my java files.
Click to expand...
Click to collapse
So far I've used Eclipse, but for my next project I'm going to try Android Studio as well, mainly because of its much easier gradle built system so that you can create multiple versions easily. I feel that gradle, the only major difference between the two IDEs, is a bit complicated to get started but can give great results once fully understood...
SimplicityApks said:
So far I've used Eclipse, but for my next project I'm going to try Android Studio as well, mainly because of its much easier gradle built system so that you can create multiple versions easily. I feel that gradle, the only major difference between the two IDEs, is a bit complicated to get started but can give great results once fully understood...
Click to expand...
Click to collapse
I haven't heard of gradle. I just Googled it and saw that it is automated deployment builds for your app. Hmm, it certainly does sound confusing.
Don't know how much of regular-Java (not android) development You do - but for me personally the best IDE is the JetBrains IntelliJ (no - I'm not their employee ) - the base for Android Studio. If You look at the basic level both Eclipse / IntelliJ have pretty much the same functions - however the latter one does lots of stuff more intelligently (I'm in love with refactoring shortcuts ). I would also expect that Android Studio will be a bit more stable than Eclipse (I used to overkill it with too many plugins).
WittyPotato said:
Don't know how much of regular-Java (not android) development You do - but for me personally the best IDE is the JetBrains IntelliJ (no - I'm not their employee ) - the base for Android Studio. If You look at the basic level both Eclipse / IntelliJ have pretty much the same functions - however the latter one does lots of stuff more intelligently (I'm in love with refactoring shortcuts ). I would also expect that Android Studio will be a bit more stable than Eclipse (I used to overkill it with too many plugins).
Click to expand...
Click to collapse
Interesting. I'll have to check that out. I wonder why IntelliJ isn't used more for Android Development.
Paul22000 said:
Interesting. I'll have to check that out. I wonder why IntelliJ isn't used more for Android Development.
Click to expand...
Click to collapse
Hi Paul,
AndroidStudio is built using IntelliJ. I'm very new to android development (started out a month ago after almost 2 years on the xda forums decided it was time to embark!) I've been using it from the start, i have eclipse to make sure its android studio that causes any bugs instead of my code. However seasoned developers obviously don't need this back-up plan!
Hope this helps.
Bassbase said:
Hi Paul,
AndroidStudio is built using IntelliJ. I'm very new to android development (started out a month ago after almost 2 years on the xda forums decided it was time to embark!) I've been using it from the start, i have eclipse to make sure its android studio that causes any bugs instead of my code. However seasoned developers obviously don't need this back-up plan!
Hope this helps.
Click to expand...
Click to collapse
You are using Android Studio or IntelliJ? So far what bugs have you encountered that were caused by the IDE and not your code?
I've been using Android Studio as my exclusive IDE and i love it. Way better than Eclipse in my opinion.
It's a beta, but i haven't found any dealbreaker yet. Some errors have appeared (non intrusively, just a popup on the top right), but they haven't affected my workflow.
It is perfectly usable to code, compile (debug and release), sign the apks and use proguard if you want. You just need to come to grips with gradle, at least on a basic level (as i have). All the build process is managed via gradle, so Android Studio doesn't get in the way.
Syncd said:
It is perfectly usable to code, compile (debug and release), sign the apks and use proguard if you want.
Click to expand...
Click to collapse
Ahh, great to hear!
Paul22000 said:
You are using Android Studio or IntelliJ? So far what bugs have you encountered that were caused by the IDE and not your code?
Click to expand...
Click to collapse
Using Android Studio.
Bug wise i've not encountered many, One rather annoying one for me was that it is irritatingly long-winded to change your minSDKversion in AS. its no just a simple case of changing the manifest file. The actualy app developers out there will know what your developing for already, me as a beginner did not and it took me the best part of an hour googling and trying things to get it to change from api7 to api14.
I'm currently still embarking on my own reading through tutorials etc and its slow going. My aim (In case anyone is interested) is to develop a stable DAW (digital audio workstation) for android. with the ability to add notes (similar to soundcloud) and cloud backup (via dropbox hopefully unless googleDrive is the more stable connection.. working on it!) So i've had no end of strangle cod bugs crop up. But from what i can see, all others have been through my bad coding / lack of knowledge!
I'll update you with any other quirks i find along the way!
Bassbase said:
Using Android Studio.
Bug wise i've not encountered many, One rather annoying one for me was that it is irritatingly long-winded to change your minSDKversion in AS. its no just a simple case of changing the manifest file. The actualy app developers out there will know what your developing for already, me as a beginner did not and it took me the best part of an hour googling and trying things to get it to change from api7 to api14.
I'm currently still embarking on my own reading through tutorials etc and its slow going. My aim (In case anyone is interested) is to develop a stable DAW (digital audio workstation) for android. with the ability to add notes (similar to soundcloud) and cloud backup (via dropbox hopefully unless googleDrive is the more stable connection.. working on it!) So i've had no end of strangle cod bugs crop up. But from what i can see, all others have been through my bad coding / lack of knowledge!
I'll update you with any other quirks i find along the way!
Click to expand...
Click to collapse
Good to know about changing the api version, thank you. I appreciate you sharing your experiences.
I'm using Eclipse exclusively. I'll use Android Studio but the time it reaches version 1.1.
Paul22000 said:
Right. But what are the actual issues with it? Just being in beta doesn't really say much. Gmail was in beta for almost a decade.
Click to expand...
Click to collapse
The main issue is no NDK support, the rest is now pretty much on-par with Eclipse feature-wise.
I've been using AS exclusively since about 2 weeks after the I/O and I really haven't looked back since. The refactoring options and code inspection is so much more thorough and well-though than on Eclipse, plus the UI (with the Darcula theme) is really a lot nicer to work with and enjoyable to use than the kinda of outdated look of Eclipse.
I only go back to Eclipse when I need to compile native code or projects which contain native code.
Once you get used to gradle it's really a pleasure, just give it some time.
EDIT: NDK support was recently added
Androguide.fr said:
The main issue is no NDK support, the rest is now pretty much on-par with Eclipse feature-wise.
I've been using AS exclusively since about 2 weeks after the I/O and I really haven't looked back since. The refactoring options and code inspection is so much more thorough and well-though than on Eclipse, plus the UI (with the Darcula theme) is really a lot nicer to work with and enjoyable to use than the kinda of outdated look of Eclipse.
I only go back to Eclipse when I need to compile native code or projects which contain native code.
Once you get used to gradle it's really a pleasure, just give it some time.
Click to expand...
Click to collapse
Ah the NDK. I think that seals the deal. I don't use the NDK nor am I planning to so it seems there is really no reason for (most) people to use Eclipse.
does anyone know when version 1 will be released?
Same, only using Android Studio.
It's great really, just takes a long time opening. But hey, it's not like Eclipse was such a performance beast.
Just make sure you get the latest builds (they release an update every week).
Related
Google, Linux , Cyanogen...all on git. I want to know why
Just spent a couple of hours setting up an example repo, found it extremely hard to use (on Windows 7). Very un-intuitive. Commands have to be typed into a linux shell to do the simplest things!!
Why not use SVN or CVS or something similar?
Only reason I can think of is that these are linux projects and hence it fits right in.
I personally use Git for everything as well (although I am a Linux developer). Here are some reasons to use it over CVS/SVN:
https://wincent.com/wiki/Git_advantages
deleted
Once you learn git, svn ain't ****.
SVN and CVS are dead, its all about Git or Mercurial these days. If you need a GUI interface for them, you shouldn't be coding.
Are you sure, there is no GUI for git? I have git support in plugins for Eclipse and Netbeans (graphical, of course), so it is hard to believe for me, that there isn't any standalone tool.
Ahh and I don't use these plugins, because I don't trust GUI ;-)
[EDIT]
And I agree with others: git, mercurial, etc. are next generation of VCS, they are just better.
The only thing git lacks (for me) is something like Tortoise. There's a project called "Git-Cheetah" being run out of the msysGit project but it's not there yet. I just keep a PowerShell window open while I'm working and it's been fine.
In the Android context, git is popular with the community--at least in part--because it's the RCS of choice of the Android Open-Source Project, which likely chose it for the same reason as Linus and friends wrote it--they wanted a fast RCS for working on a large codebase. No question git is fast.
There are certain advantages to using non-distributed RCS in some environments, especially where configuration management is a concern (guaranteed monotonic revision numbers!) However, git works wonderfully in less-formal environments--and yes, Linux kernel development is informal from a process standpoint.
Anyone using CVS on a new project should be publicly castigated. There's no good reason to use that when you have Subversion.
(Personally, I would like darcs to see more use, but the speed thing is a problem. They do claim to be working on it.)
britoso said:
Commands have to be typed into a linux shell to do the simplest things!!
Click to expand...
Click to collapse
Well that is somehow a mute argument. This is how many people work most of their day, at work or at home (both in my case - and, please, I'm no programmer). I do understand that it is not really intuitive, especially if you are not only coming from the windows world but also try to use these utilities from within windows. The projects you mention are all Linux projects, so they of course use a *nix utility to handle their code.
Yeah it's a pain to try to do something with cygwin and if you only use it for compiling or checking out code you don't really know how to operate it anyway. That of course makes it hard to handle unexpected results that weren't covered in the how-to.
Fortunatly you can always ask somebody or at least read the man page. This is how linux works, you have to find out stuff yourself. For many tools there will probably be no GUI and if there is, it sucks
try Bazzar it might work for you http://wiki.bazaar-vcs.org/BzrVsGit#Overview
Bazaar, on the other hand, includes a native Windows port and installer. The port feels like a regular Windows program, and the installer includes the graphical front end for Windows, TortoiseBzr. Olive is available as a graphical front end for Linux.
Click to expand...
Click to collapse
There is in fact a tortoisegit project I haven't posted enough before so I can't post a real link yet.
h t t p : / / code.google.com/p/tortoisegit/
I've got it installed and it seems to work fairly well.
GelatinousSlime said:
There is in fact a tortoisegit project I haven't posted enough before so I can't post a real link yet.
http://code.google.com/p/tortoisegit/
I've got it installed and it seems to work fairly well.
Click to expand...
Click to collapse
Very nice.
shwan_3 said:
try Bazzar it might work for you http://wiki.bazaar-vcs.org/BzrVsGit#Overview
Click to expand...
Click to collapse
http://doc.bazaar.canonical.com/explorer/en/
Good to know. But I just want to try the Android code, which is on git.
is there a way to port / recompile OpenOffice for Android?
There are a lot of good and great applications that are linux native out there.
I'm rather surprised we don't see more of those software like OpenOffice / FireFox / Thunderbird ported over for Android.
i was soooo looking forward to run those on my phone.
i know some groups are already working on a mobile version of firefox (Fennec), but there's no news about Thunderbird, and according to some stuff i read on the OpenOffice forum they don't seem very eager to port it to Android, as it took them a while to port it to MAC OS.
yet it's still a java based app... oh well...
at the moment i'm using "Docs To Go", not ideal, but it does for now, until OpenOffice comes aboard.
I've been using Docs To Go since my PalmOS days, is not bad, but is not great either.
docs to go seem to have worsen from palm to winmo to android. the android version is all flashy with smooth scrolling, pinch zoom etc but actual functionality is lacking. for eg; in the spreadsheet - editing is cumbersome, changing worksheets need few presses.
still looking for a good office suite/spreadsheet for android.
A lot of software like that is not written to run on low-powered systems (which an android phone clearly is compared to todays PCs) and Android lacks a lot of functionality that is present in complete linux kernels and so rewriting would take a major effort and few people would benefit from an open-office port (and even if, they would be minor since nobody will actually do a lot of office work on their phone).
AllGamer said:
is there a way to port / recompile OpenOffice for Android?
There are a lot of good and great applications that are linux native out there.
I'm rather surprised we don't see more of those software like OpenOffice / FireFox / Thunderbird ported over for Android.
Click to expand...
Click to collapse
Unfortunately, Android is to Linux as Windows Mobile is to Windows 7. They're related, but not strictly intercompatible.
Android only really uses the Linux kernel. Practically none of the stuff that makes Linux recognisable as Linux to end-users. For Open Offic, Firefox etc to work as a simple port, you would need a whole bunch of extra stuff in Android that just isn't there. Of course, that's not stopping anyone from porting those things, but Android with X11, GTK and Gnome wouldn't really be Android anymore, would it?
Of course, I feel your pain.. I just want a simple text editor that can open and save .txt files, but I can't find one! Bah!
unfnknblvbl said:
Unfortunately, Android is to Linux as Windows Mobile is to Windows 7. They're related, but not strictly intercompatible.
Android only really uses the Linux kernel. Practically none of the stuff that makes Linux recognisable as Linux to end-users. For Open Offic, Firefox etc to work as a simple port, you would need a whole bunch of extra stuff in Android that just isn't there. Of course, that's not stopping anyone from porting those things, but Android with X11, GTK and Gnome wouldn't really be Android anymore, would it?
Of course, I feel your pain.. I just want a simple text editor that can open and save .txt files, but I can't find one! Bah!
Click to expand...
Click to collapse
Linux IS only really the kernel.
kevo said:
Linux IS only really the kernel.
Click to expand...
Click to collapse
Still, in this context it clearly refers to any desktop linux distribution. And that comprising isn't far off.
Sent from my GT-I9000 using XDA App
It's been done
AndrOpen Office
Download: https://market.android.com/details?id=com.andropenoffice
Sent from my GT-N7100 using XDA Premium 4 mobile app
I've been considering getting into Android development for quite awhile now. I've read multiple tutorials/guides around the internet and would like to jump into it. I would like some input as to what my first project should be as well as any advice you guys may have. I've used the desktop version of Ubuntu multiple times in the past. Although it's not my favorite desktop Linux distribution, I'm quite interested in trying Ubuntu Touch on my N910T. On the other hand, I really like straight up Vanilla AOSP. So what do you guys think?
kaden93 said:
I've been considering getting into Android development for quite awhile now. I've read multiple tutorials/guides around the internet and would like to jump into it. I would like some input as to what my first project should be as well as any advice you guys may have. I've used the desktop version of Ubuntu multiple times in the past. Although it's not my favorite desktop Linux distribution, I'm quite interested in trying Ubuntu Touch on my N910T. On the other hand, I really like straight up Vanilla AOSP. So what do you guys think?
Click to expand...
Click to collapse
well i doubt you would get many users for ubuntu and aosp takes years of development to work properly on any branded devices sooooooooo lol
I vote Ubuntu touch becuase. Ive seen a million AOSP roms. Ive seen 0 ubuntu touch roms
Ubuntu!
I still want to see AOSP with the TW camera and sPen ported. I figure its near impossible otherwise someone would have done it by now but I am still hoping.
Sent from my SM-N910T3 using XDA Free mobile app
Ubuntu +1
Sent from my SM-N910T using Tapatalk
Yeah, I was leaning more toward Ubuntu Touch. There's no reason not to try at this point. As part of that, does anybody know any good tutorials for setting up the source repositories? I was able follow the CyanogenMod build guide without any issues, but I'm still trying to understand the build environment structure. Thanks for the feedback.
Hello everyone!
I'm kinda new to android game development and after reading a few guides I managed to successfully create a game in eclipse.I then decided to give android studio a shot and make an app for the google playstore but it's so different then the eclipse and there are a lot fewer tutorials for game development in android studio., which makes it a bit hard to learn.Should I code in Eclipse or transition to android studio for apps?What do you guys think?What are main advantages of android studio?
Thanks in advance!!!
igorcar1994 said:
Hello everyone!
I'm kinda new to android game development and after reading a few guides I managed to successfully create a game in eclipse.I then decided to give android studio a shot and make an app for the google playstore but it's so different then the eclipse and there are a lot fewer tutorials for game development in android studio., which makes it a bit hard to learn.Should I code in Eclipse or transition to android studio for apps?What do you guys think?What are main advantages of android studio?
Thanks in advance!!!
Click to expand...
Click to collapse
Android Studio is not as powerful as Eclipse yet, but a lot of online tutorials and courses remake their lessons with using of Android Studio. Also this IDE is growing really very fast and Google is oriented on it, so i prefer Studio. This is more comfortable to work with.
For game development, there's hardly any difference between using Eclipse or IntelliJ IDEA. All you really need is to be able to import your Android project (potentially Gradle-based), run and debug it, edit code, and provide syntax highlighting and auto-completion. Both Eclipse and IntelliJ IDEA support all of this. The rest of the tutorials you've read should be applicable to both IDEs. If not, you should look into better tutorials. There's no reason to make Android game development IDE specific.
igorcar1994 said:
Hello everyone!
I'm kinda new to android game development and after reading a few guides I managed to successfully create a game in eclipse.I then decided to give android studio a shot and make an app for the google playstore but it's so different then the eclipse and there are a lot fewer tutorials for game development in android studio., which makes it a bit hard to learn.Should I code in Eclipse or transition to android studio for apps?What do you guys think?What are main advantages of android studio?
Thanks in advance!!!
Click to expand...
Click to collapse
Hello,
I will suggest you to move to Android Studio. Eclipse platform is no more supported by Google and Google promotes Android Studio.
A lot of tutorial are moving to Android Studio.
IMHO, there is no big differences between these 2 IDEs. I used to code with Eclipse and when I moved to Android Studio, I almost saw no difference.
However, if you want to develop games Eclipse or Android Studio is not the problem. The problem is to find a good game framework.
I recommend you to use : libGdx. A great framework to develop games in Android !
Regards,
Hello XDA Community,
I am interested in using the unofficial build of CyanogenMod 14.1 available here, but I would like to learn how to compile on my own from the repository provided by the developer. Unfortunately, I do not know how to go about doing this. Could someone please help me out? I have looked at the CyanogenMod Wiki entry for how to compile CyanogenMod for the Nexus 6, but the information is out of date according to what I was told in a post I made on Stack Exchange's Android Q&A site. The only thing that I understand about the build process is that I need to use Linux, so I have set up a virtual machine in VMware running the latest version of Ubuntu. Where do I go from here?
Thank you,
David B.
David B. said:
Hello XDA Community,
I am interested in using the unofficial build of CyanogenMod 14.1 available here, but I would like to learn how to compile on my own from the repository provided by the developer. Unfortunately, I do not know how to go about doing this. Could someone please help me out? I have looked at the CyanogenMod Wiki entry for how to compile CyanogenMod for the Nexus 6, but the information is out of date according to what I was told in a post I made on Stack Exchange's Android Q&A site. The only thing that I understand about the build process is that I need to use Linux, so I have set up a virtual machine in VMware running the latest version of Ubuntu. Where do I go from here?
Thank you,
David B.
Click to expand...
Click to collapse
To be honest You will be better off dual booting. Compiling with a VM normally has more issues then not.
Then I would look at Google developer page.
Also keep in mind that compiling from CM means you get all the bugs they never fixed. You would be better off going with AOSP and then finding the features you want to add and then add them yourself.
zelendel said:
To be honest You will be better off dual booting. Compiling with a VM normally has more issues then not.
Then I would look at Google developer page.
Also keep in mind that compiling from CM means you get all the bugs they never fixed. You would be better off going with AOSP and then finding the features you want to add and then add them yourself.
Click to expand...
Click to collapse
I would love to build my own CyanogenMod based on AOSP and then merge in the features, but I don't even know how to build directly from AOSP.
Honestly, all I really want is stock with all of the additional developer mode features that CyanogenMod has along with root access. I love the ability to use root without extra apps, and wireless ADB is sweet when I'm too lazy to go get my USB cable. And of course, I want to be able to use future versions of Android on my phone even though 7.0.1 is supposed to be the last version for Shamu. Could I somehow merge those aspects together and just pull patches from AOSP, build, and flash?
Also what's wrong with using a VM to compile? I've read that problems occur if you don't have enough RAM allocated to the VM, but I've assigned it 16GB so that should not be a problem. As for attaching my phone to the VM, I am using VMware, which has better support for removable devices than VirtualBox.
I'm sorry if I misunderstand something you said. It's probably obvious, but I know pretty much nothing about what I am doing which means I'm likely to ask lots of questions that seem ridiculous to those that are well-versed in this sort of thing.
David B. said:
I would love to build my own CyanogenMod based on AOSP and then merge in the features, but I don't even know how to build directly from AOSP.
Honestly, all I really want is stock with all of the additional developer mode features that CyanogenMod has along with root access. I love the ability to use root without extra apps, and wireless ADB is sweet when I'm too lazy to go get my USB cable. And of course, I want to be able to use future versions of Android on my phone even though 7.0.1 is supposed to be the last version for Shamu. Could I somehow merge those aspects together and just pull patches from AOSP, build, and flash?
Also what's wrong with using a VM to compile? I've read that problems occur if you don't have enough RAM allocated to the VM, but I've assigned it 16GB so that should not be a problem. As for attaching my phone to the VM, I am using VMware, which has better support for removable devices than VirtualBox.
I'm sorry if I misunderstand something you said. It's probably obvious, but I know pretty much nothing about what I am doing which means I'm likely to ask lots of questions that seem ridiculous to those that are well-versed in this sort of thing.
Click to expand...
Click to collapse
You do know that there is an app for SU built into CM right? So it is no extra apps then any other rom.
Could you yes but it will be lots of work due to what CM changes in the source code. It is one of the many reasons (on top of years old bugs that were never fixed) That many teams stopped using them as a source. The Shamu will be supported by 3rd party developers for a while to come.
Normally ram is an issue but other issues also happen.
I dont know anything about having to attach your device to VM as I have never used VM due to advise from the developers here.
Asking questions is not that big of a deal as long as you do your research. There are tons of TUT on the site about setting up a build setup. Just use the search and spend a few days reading. Mainly where the licenses are concerned. Also commit authorship. Which is you make your own rom it is very important.
zelendel said:
You do know that there is an app for SU built into CM right? So it is no extra apps then any other rom.
Could you yes but it will be lots of work due to what CM changes in the source code. It is one of the many reasons (on top of years old bugs that were never fixed) That many teams stopped using them as a source. The Shamu will be supported by 3rd party developers for a while to come.
Normally ram is an issue but other issues also happen.
I dont know anything about having to attach your device to VM as I have never used VM due to advise from the developers here.
Asking questions is not that big of a deal as long as you do your research. There are tons of TUT on the site about setting up a build setup. Just use the search and spend a few days reading. Mainly where the licenses are concerned. Also commit authorship. Which is you make your own rom it is very important.
Click to expand...
Click to collapse
Okay, so I have done some research and have a solution for how to use root with stock Android, but as soon as stock Android support is dropped from the Nexus 6 I will have to compile it myself which I am not sure how to do and would like to learn. Do you have any suggestions for what to go to learn since everything I am finding is not about compiling, but is instead about using an existing build?
David B. said:
Okay, so I have done some research and have a solution for how to use root with stock Android, but as soon as stock Android support is dropped from the Nexus 6 I will have to compile it myself which I am not sure how to do and would like to learn. Do you have any suggestions for what to go to learn since everything I am finding is not about compiling, but is instead about using an existing build?
Click to expand...
Click to collapse
Here you go
https://source.android.com/source/initializing.html
Mind you getting root is more then adding an app for it. You will also have to do some kernel edits.
zelendel said:
Here you go
https://source.android.com/source/initializing.html
Mind you getting root is more then adding an app for it. You will also have to do some kernel edits.
Click to expand...
Click to collapse
Thanks! I also found this. I have not really looked at it too much yet, but it seems like it has the potential to help me with what I want. Why would I need to make kernel edits? I thought all I needed to do was use TWRP to flash SuperSU after flashing the ROM.
David B. said:
Thanks! I also found this. I have not really looked at it too much yet, but it seems like it has the potential to help me with what I want. Why would I need to make kernel edits? I thought all I needed to do was use TWRP to flash SuperSU after flashing the ROM.
Click to expand...
Click to collapse
SuperSU edits the kernel when you flash it. Most of what allows root is in the kernel.
Yes that is a great resource. Just take your time and read it. You could have a working set up and build in about 2 days (given the first sync of the source code could take more then 24 hours depending on your connection.
zelendel said:
SuperSU edits the kernel when you flash it. Most of what allows root is in the kernel.
Yes that is a great resource. Just take your time and read it. You could have a working set up and build in about 2 days (given the first sync of the source code could take more then 24 hours depending on your connection.
Click to expand...
Click to collapse
One thing that I still cannot figure out after all of this reading is what to do to get AOSP to build for devices that are not officially supported by it. Granted, this is not a problem for the Nexus 6 right now, but it will be eventually, and I want to know how to handle it when it does become an issue. I've started cloning the repository. My connection gets a top download speed of 60Mbps so it should be reasonably fast.
David B. said:
One thing that I still cannot figure out after all of this reading is what to do to get AOSP to build for devices that are not officially supported by it. Granted, this is not a problem for the Nexus 6 right now, but it will be eventually, and I want to know how to handle it when it does become an issue. I've started cloning the repository. My connection gets a top download speed of 60Mbps so it should be reasonably fast.
Click to expand...
Click to collapse
At that point you will need to know what you are doing as you will have to make the code changes to make it bootable. I hate to say it but the n6 maybe doa after this as anything after 7.1 will need dual partition setup which the n6 doesn't have
zelendel said:
At that point you will need to know what you are doing as you will have to make the code changes to make it bootable. I hate to say it but the n6 maybe doa after this as anything after 7.1 will need dual partition setup which the n6 doesn't have
Click to expand...
Click to collapse
What's stopping the phone from being repartitioned in the same way you repartition a hard drive?
David B. said:
What's stopping the phone from being repartitioned in the same way you repartition a hard drive?
Click to expand...
Click to collapse
The main issue is none of the software for the n6 are made to work with it. All the drivers have to be rewritten. Also all of the new Vulcan graphics drivers won't work on the n6. This is why it didn't get all the features of 7.0
zelendel said:
The main issue is none of the software for the n6 are made to work with it. All the drivers have to be rewritten. Also all of the new Vulcan graphics drivers won't work on the n6. This is why it didn't get all the features of 7.0
Click to expand...
Click to collapse
I had not heard of this before. I was researching it online a bit and I cannot figure out which features are missing from the Nexus 6 version of Nougat. Also, Nougat has to support older hardware for devices that don't support Vulkan, so there's no reason they can't do that for Android O, and it they don't, surely someone smarter than I will be able to hack it together.
David B. said:
I had not heard of this before. I was researching it online a bit and I cannot figure out which features are missing from the Nexus 6 version of Nougat. Also, Nougat has to support older hardware for devices that don't support Vulkan, so there's no reason they can't do that for Android O, and it they don't, surely someone smarter than I will be able to hack it together.
Click to expand...
Click to collapse
That's the thing is android O will only be official supported by devices that can use it. Remember the nexus 6 support ended in October so there won't be an official O release for it.
Will there be a hacked together set up? Oh I'm sure there will be. It will just be without the Vulcan graphics drivers and the new update system which needs the dual partition layout.
The missing features are no background updates, no Vulcan drivers among other things
zelendel said:
That's the thing is android O will only be official supported by devices that can use it. Remember the nexus 6 support ended in October so there won't be an official O release for it.
Will there be a hacked together set up? Oh I'm sure there will be. It will just be without the Vulcan graphics drivers and the new update system which needs the dual partition layout.
The missing features are no background updates, no Vulcan drivers among other things
Click to expand...
Click to collapse
Well if the only things I lose are Vulkan and background updates, I am cool with that. It sounds like Vulkan is intended for games, and since I hate mobile gaming, an adapted build that works with the existing graphics drivers is not a concern at all. As for background updates, I would rather not have those because I like to know when my phone receives updates.
David B. said:
Well if the only things I lose are Vulkan and background updates, I am cool with that. It sounds like Vulkan is intended for games, and since I hate mobile gaming, an adapted build that works with the existing graphics drivers is not a concern at all. As for background updates, I would rather not have those because I like to know when my phone receives updates.
Click to expand...
Click to collapse
The Vulcan driver will be replacing the graphics drivers for everything soon. I can't think of much as I never use stock software.
zelendel said:
The Vulcan driver will be replacing the graphics drivers for everything soon. I can't think of much as I never use stock software.
Click to expand...
Click to collapse
I am sorry, but I am afraid I do not quite understand what it is that you said. What can't you think of?
David B. said:
I am sorry, but I am afraid I do not quite understand what it is that you said. What can't you think of?
Click to expand...
Click to collapse
There were many features that came with 7.0 like the new advanced doze and some other stuff. I dont use stock software and to be honest most of the stuff from 7.0 wasnt even really worth the update to me.
I have had a nexus since day 1 on and off and this was the first time I wasnt excited about the update. Even less with the new updates coming and google locking android down more as well as them moving most of the new stuff to closed sourced stuff. Heck even just having the bootloader unlocked is causing things not to work.
zelendel said:
There were many features that came with 7.0 like the new advanced doze and some other stuff. I dont use stock software and to be honest most of the stuff from 7.0 wasnt even really worth the update to me.
I have had a nexus since day 1 on and off and this was the first time I wasnt excited about the update. Even less with the new updates coming and google locking android down more as well as them moving most of the new stuff to closed sourced stuff. Heck even just having the bootloader unlocked is causing things not to work.
Click to expand...
Click to collapse
Really? What doesn't work with the unlocked bootloader?
David B. said:
Really? What doesn't work with the unlocked bootloader?
Click to expand...
Click to collapse
Things like android pay and saftynet. They are now starting to look for unlocked bootloaders. then you have those that are blocking apps due to root or xposed.