I'd like to make Android Go instead of using AOSP.
But have no information except this site (https://www.android.com/versions/go-edition/)
Please let me know any hint or contact points if any.
Can I compile Android Go from my AOSP code?
Do I need to contact google person to get some right to handle Android GO source code?
Thanks
As long as I know Android Go Edition is a Trimmed down lighten version of AOSP to run on Low-end chips with more optimization in code than AOSP which are tends to run on High-end SoC's but that is done all on Manufacturers side Google don't provide this.
But you can contact Google to know more about it and If you are planning to Launch a device.
Related
Does anyone know if Google provides an API to configure the AON on the S8 and similar devices?
On the Display documentation I didn't find anything.
I was wondering if someone had experience creating app that make changes like, adding text, positioning image adding an app icon etc (I know the stock features do provide some of these features but I wanted to know if it was possible to do this by creating a third party app)
Thanks
After doing some research I came across a guy who has been doing some development on the Always On Display. On XDA forum he has an app that does exactly what I am looking for and he has been kind enough to provide some further info.
It's an overlay targeting the AOD, you can build overlays either by
manually adding code with Apkeditor (app) or build an overlay with
Android Studio, my mods are built with Android Studio.
There's a substratum template that should help you themeing apps.
(With overlays) https://github.com/substratum/template
I have an assignment to take source code of CyanogenMod for certain device, to do some changes (at first, to disable tethering, set custom launcher that my team made, etc...). I managed to get source of CM, rebuilt it and flashed the device with it. I didn't use LineageOS deliberately, since its version is very unstable for this device.
Now, I wish to make some aforementioned adjustments and build ROM with these changes, could someone please point me to the right direction how to achieve it? I couldn't find anything similar to this on the net.
Thanks!
If it's not too late:
you need to find your phone here :
https://wiki.lineageos.org/devices/
and then go to https://wiki.lineageos.org/devices/addison/build
(change addison by your device codeName, which you can find in the "DEVICES" part of this website)
you will find all instructions to build lineageos from sources for your phone, you can then modify these sources to add your custom launcher, disable anything you want...
Cheers
I am a android beginner. I am going through the book listed in the title. I haven't even made it past the first chapter without running into problems. I have installed the latest version of Eclipse. However, the examples shown in the book are not much like my version. For instance, this main.xml file that's supposed to be in the layout folder is not there. The "New Android Project" dialog box is arranged very differently and the package explorer is called project explorer. Is there a way to get this kind of eclipse in the book? Or do I just have to interpret it best I can? Any help would be much appreciated! This question has been down voted and closed by another user. Could someone please tell me why? I am just trying to get some help.
As different Android APIs(ICS, JB, etc.) are released, they sometimes change the ADT (Android Development Tools) for Eclipse. The ADT is plugin for Eclipse. This plugin is what gives you all those neat buttons in the toolbar and the XML layout interaction.
The book you are reading was designed for Android 4.0(Ice Cream Sandwhich). As of right now, Google has released up to Android 4.2.2(JB 4.2). There has been some significant changes to the ADT going from ICS to JB, but in my opinion, they are for the good. Lots of really neat and new features. Here is a Google resource explaining the different API releases for Android: http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels
I would say continue reading the book as it will teachs you the basics of Android, but when you want to do some in depth coding, that book isn't going to be very useful and you may have to do a little research online. Reason is, Google releases at least two new versions of Android every year. Every version changes, and adds new features. In other words, the book you are reading is already out of date. Android OS development moves way to fast for authors to keep updating their books.
To answer your question, your probably going to have to interpret it the best you can since, most likely, by June/July, Key Lime Pie is going to out, and the ADT your using NOW will be outdated. You should really learn the fundamentals of Android OS and how it works in the background and how processes things. After that, everything else should be easier to learn.
An alternative to the book you are reading is this: http://developer.android.com/training/basics/firstapp/index.html. This is straight from Google and is constantly updated and tweeked. This will be the most updated and useful information on how to write Android apps.
Hope that helps!
Okay here's the deal:
I want to download the full source of the MMS/SMS application that ships with Android phones. I want to be able to modify it, and add a little custom functionality to it.
I am developing using Eclipse, and I'm on Windows 7. I have noticed that there is now a Git for Windows, but I am pretty lost in it and not sure how to integrate everything with Eclipse.
Basically, I want to just get it to the point where I have all the source code visible in Eclipse and be able to see the app run JUST like the built-in texting/MMS app that is already on my phone. Then I'll know that I can modify it and proceed.
Any ideas?
Thanks!
There's a mirror of the SMS/MMS app on GitHub here. Just import that to Eclipse and customise away.
Unless you want to customize and use it only on your own phone (without publishing), this is not a good idea. This is because it uses classes that are hidden from the sdk. By default you won't even be able to build the apk via eclipse, but there is a way. The reason why this is a bad idea is that the hidden apis are not guaranteed to remain the same through different api-levels and your app can stop working with the next android update, and might also not work on previous api-levels. In-fact your app might not even work on selected phones running the same api-level.
I have download a set of android source code, which has folders such as "bionic, bootable, build, dalvik, development, frameworks, hadware, packages, prebuilt" and so on. When I browse the whole code, wonder how "import android.preference.PreferenceActivity;" works in Settings.java(D:\android-srce\Google-source\packages\apps\Settings\src\com\android\settings\Settings.java). I guess there is a android.jar file somewhere after compilation. But how does Settings.java import PreferenceActivity correctly?? I'm a beginner in Android, please help me.
Sounds like you have downloaded the source code to the Android OS. If you want to build your own ROMS then you need to study about building the OS for a particular hardware platform. This is not trivial.
If you want to build an Android app that runs on an Android device then you want to download the SDK instead - start at Android SDK and follow your nose, buy a book, read the sample code.
There is not a lot of information how to change parts of Android. However, you can read information that is connected with the aosp tag. The first cite is source.android.com After the installation of android build system you can see video from marakana group. You'll find a lot of valuable information there.