I want to make changes to AOSP multi-window feature.
I would like to know how do we make those Changes?
Also, I would like to know after making changes to AOSP how do I flash the modified AOSP on my device.
Flashing AOSP based ROM will require device vendors. Then you need configure Your device and create custom make files. All about adding new device is here. I think You should follow these instructions, apply Your changes, run system on emulator and then try to extract Your vendors.
Related
Other than using an MDM service or product, is there a way to automate the mass setup of android devices that all need the same configuration?
Requirements:
APK installation (in-house app)
Profile setup (lockscreen setup, screen brightness, etc.)
Customization (wallpaper, icon placement, removal of unwanted default apps)
I am only familiar with Samsung solutions.
For exactly this purpose Knox Configure has been created. You can setting up big bunch of phones without even opening the boxes.
So if you use Android Samsung devices take a look:
https://www.samsungknox.com/en/solutions/knox-configure
Update: Google introduced Zero Touch with Android Oreo
https://www.android.com/enterprise/management/zero-touch/
I would like to compile my own pure AOSP (Android 5.0 or 5.1) ROM for my Samsung Galaxy S4 Mini (serranoltexx). I read something about this here but I have a few more questions. I searched for the nessesary files on GitHub and found this here:
Device tree
Vendor files
These are CM files so can I use them for an AOSP build? And do I have to change some of these files or can I use them to build my ROM without any changes? And also these files are for CM 12 (5.0.2) and maybe I want to compile a 5.1 ROM. Can I also use them for the new version of Android?
The device and vendor files are not really part of the AOSP, so you should have no trouble making the vanilla AOSP while including these specific trees. If a vanilla AOSP doesn't include your device in the available options, however, none of the source will use these device and vendor products to poll and use hardware features included in the 3rd party trees, so the end effect will be no new functionality.
Part of porting would be to make sure the specific projects in the AOSP use the specific hardware features when necessary, as there is nothing there to tell it otherwise. Though these may work to enable specific cameras, or graphics drivers, etc, you won't get any extra functionality, other than the fact the devices exist (which may be enough).
To include these projects in the build, you'll have to edit one of the main make files in the build/target/product directory of the AOSP. Ideally, you'd have your product specified here, but if you do not, you can add it to a generic makefile therein. See this post for info that will set you on the right path.
This is a bit of a hack, and ideally you would be better off editing the setup scripts to be able to 'lunch' for your device. The scope of this is well beyond this post, but is covered by Karim Yaghmour's excellent Embedded Android.
Hope this at least sets you off in the right direction!
You have to include CAF patches into AOSP rom. See, Google supports pixel,nexus,Mi A1, Motorola etc devices. You have to include you device specific proprietary and then you have to compile, You can boot AOSP ROM too goto codeaurora doumentation and icludin their patches.
I can't find a clear list of what files needs developer's attention when i'm building a new Android image.
All the guides that i have found until now are way too generic or really old.
I'm supposing that i'm not interested on customize the platform, i just want a vanilla flavour but for my device only.
The answer is a bit complicated. You probably cannot build a vanilla Android for your device, unless your device is one of the google developer phones. Here is a list of the devices you can build Android for. The reason being that the manufactures usually does not publish all the parts needed to actually build Android for their devices.
But do have a look at the cyanogenmod project, and see if they support your device. They are kind of trying to make a "vanilla" android source for the devices which the manufactures themselves does not support. And they are doing quite a nice job, in my opinion. I have a custom build of Android 4.0 for my Galaxy SII running for months now, and it is working perfectly fine.
If you update your questions with the devices your are using, I can probably provide specifics on how you can build cyanogenmod for your specific device.
What are you trying to do ?
Declare some images or layout specific to only one device ?
You can't do it with a selector on a folder (-large, -fr, ...), but with some code. Check this out : http://developer.android.com/reference/android/os/Build.html#MODEL,
I followed the guide on android.com and compiled the source code. Now it runs well in the emulator. There are some .img files so I think it may be viable to flash them on real devices.
But I see on the guide there is a 4th step, which is to compile some device-specific proprietary files. But my device is not on their list. So what extra work needs to be done if I want to flash the .img files to real devices rather than the emulator? Will the real devices get bricked? Thanks.
well -- that is the "difficult" part of making a custom ROM for a device. You need to have a complex understanding of the particular hardware that you're building for, and adjust and update the codebase accordingly.
That said -- a real device will (probably) not get bricked, but you will need to use the recovery image to put a working ROM back on to use the device again. Make sure you have a rooted device and a decent recovery on it (Clockworkmod)
How do i change the android´s system font configuration?
O know that it´s a kind of low level configuration, but i´m not sure where it is located.
The idea is to make an option to set the default size, for those with vision disabilities.
I need something changeable, not hard coded.
Additional Information:
-I will generate a build of the System, so would be no problem changing any system file, class, or anything necessary.
-SDK 2.2 - Froyo - API Level 8
While this is indeed a low-level config change, it isn't really that simple. First, you need to have a rooted device with BusyBox installed. XDA developers made an app (search Type Fresh in the market) that changes the default font for you. I don't believe there's an easy way to do it manually, and AFAIK it's impossible without root and busybox.