I want to build the Android Wear AOSP code and flash a watch with it, however I can't find any instructions anywhere online and I've just downloaded the Lollipop Wear AOSP code but there's no instructions downloaded that I can see.
I know how to build/flash a phone AOSP but wondering if/what is different for the Wear AOSP - for example if I type lunch I still get the same options as I do for a regular AOSP -there's nothing in there specifically for wearables as far as I can see so which combo do I pick to build it?
Then after I've built it, can it be installed using fastboot flash boot|recover|system|data images or are there different partitions/images?
Thanks for any insight.
Related
So here is what i'm trying to do.
I use to have a Galaxy Nexus with AOKP, OmniRom, etc installed as well as I have OmniRom on my 2013 N7. My current phone is a Moto X & I have the stock rom on it with xposed installed.
What I like abut Omni on my N7 is that when I go to install an apk, I get the current version installed as well as the new version installed under version info (which you can't find on stock roms). (look at the screen shot attached)
I've been interested in trying to make an xposed module to re-create this for stock roms however I have no idea where to find the string of code that inserts the current/new info you see in the screen shot. I've tried Stackoverflow, but haven't found my answer yet.
It's obviously seen in many custom roms & i'm sure many of you have seen it, but I don't know what portion of the rom it gets coded in, to be able to see what the strings look like to make it work.
Can anyone point me in the right direction? Do I need to ask a rom dev or try to ask this on stack?
I've been watching and waiting for the G900TUVU1ANCH source code on Samsung's website, but all they have available right now is G900TUVU1ANCD. Two questions:
1) How long does it typically take Samsung to release the latest version of source code after the firmware has been pushed to devices (or manufactured with said version)?
2) Are there any other avenues to obtain the source code (i.e. through carrier, via leaks, per request)?
I'm looking at trying my hand at porting native Ubuntu Desktop to the S5, but I would like to start with the current/latest kernel.
FYI, one of the reasons I moved from the S4 -> S5 was because of AT&T's ridiculously locked bootloaders, making native booting to Ubuntu Desktop or Ubuntu Touch very difficult - and impossible to make an "easy" way of switching between this and Android seamlessly (i.e. via a boot menu of sorts).
Aou said:
I've been watching and waiting for the G900TUVU1ANCH source code on Samsung's website, but all they have available right now is G900TUVU1ANCD. Two questions:
1) How long does it typically take Samsung to release the latest version of source code after the firmware has been pushed to devices (or manufactured with said version)?
2) Are there any other avenues to obtain the source code (i.e. through carrier, via leaks, per request)?
I'm looking at trying my hand at porting native Ubuntu Desktop to the S5, but I would like to start with the current/latest kernel.
FYI, one of the reasons I moved from the S4 -> S5 was because of AT&T's ridiculously locked bootloaders, making native booting to Ubuntu Desktop or Ubuntu Touch very difficult - and impossible to make an "easy" way of switching between this and Android seamlessly (i.e. via a boot menu of sorts).
Click to expand...
Click to collapse
Not sure about the platform source, but the CH release appears to use the same kernel sourced in the Samsung released labeled CD. They're both (rather erroneously) tagged as kernel version 3.4.0. I used the current source to build a kernel here http://forum.xda-developers.com/showthread.php?t=2729338 which works exactly as expected. I'm guessing CH was just a baseband release at this point.
Samsung has historically been pretty timely about pushing new sources, usually within a week or so.
Good luck.
zaventh said:
Not sure about the platform source, but the CH release appears to use the same kernel sourced in the Samsung released labeled CD. They're both (rather erroneously) tagged as kernel version 3.4.0. I used the current source to build a kernel here http://forum.xda-developers.com/showthread.php?t=2729338 which works exactly as expected. I'm guessing CH was just a baseband release at this point.
Samsung has historically been pretty timely about pushing new sources, usually within a week or so.
Good luck.
Click to expand...
Click to collapse
Gotcha. If it was indeed just a baseband update or something irrelevant to the open-source parts of the firmware, then I guess there wouldn't be anything to update on Samsung's website. I'll probably stick with the *CD source and use it like you did. Thanks.
For that matter, has anyone captured the *CD -> *CH update as a .zip? Would have required root at that time to snag it, and I came into the S5 game a few days late (not sure on the sequence of events here)... In any event, if it were captured, it would tell us exactly which components were updated, and if building stuff from the *CH source is required for anything specific.
Lastly, minor updates typically don't touch the kernel, so I think you are absolutely right, @zaventh.
Good evening all,
I came across a post on here a while ago which asked about the ability to run Gingerbread on a Nexus 7 of 2012 and the response was basically, why? And, co pile it yourself.
So, I thought I'd give it a go, just to see what it does.
Previously I've only ever flashed custom ROMs and I've never downloaded AOSP before, but everyone starts somewhere.
My position at the moment is I've built Gingerbread from AOSP on my server but as I didn't choose Nexus 7 when building it (due to it not having an option to lunch Gingerbread) I opted for the generic build.
So, this built but as it's generic it seems to only be the system, no recovery or boot.img etc.
So, I looked around at guides, building a boot.img for your device in AOSP etc, kernel compilation, but due to my bizarre project, I can't find anything on how to downgrade or retrofit a new boot.img into an older version of Android. Or even how to compile an older boot.img against newer hardware. Even the guides talk about swapping one ROM for another and taking pieces out but they tend to be the same versions of Android.
So, I'm asking for advice really, where do I start?
Sent from my Nexus 4 using Tapatalk
Quick update (not that I've done much on it for a while).
I managed to get the older Gingerbread bootloader installed on my Nexus 7 2012, however I couldn't get further then that, not sure what I'm missing at the moment, potentially the kernel isn't compiled.
So I really like google dialer and have a Samsung s5. Now the new lollipop dialer or the google dialer 2.0/2.1 won't install on a tw ROM as it would appear. So I was thinking if I could make my own build from the source I could have the dialer I want without losing the tw features. So I have successfully clone the source to my PC and imported it into android studio as a project. Every time I try to build or try to produce an apk I have 31 errors stating ”no resource...” in the style.XML. I have tried to find a guide that would help me to build an apk from source with no avail. So I am curious to what I'm missing? Some direction would be greatly appreciated.
Do you have the Android sdk installed? Even then it wont install. You have to have it as a system APP and then you will lose the TW features of the dialer.
zelendel said:
Do you have the Android sdk installed? Even then it wont install. You have to have it as a system APP and then you will lose the TW features of the dialer.
Click to expand...
Click to collapse
Well I do have SDK installed.
Ok and it is updated? I would track down the errors and just fix what is missing by comparing it to a pre-built apk
Hello... Since I'm not very familiar with cell phones I'm curious about something. With a desktop computer, one can build their own or have a manufacturer type ( Dell, HP and so ) Now if you take the custom build system you basically can decide which OS you want, why can't cell phones be similar to that be able to install whichever OS you like, Or can you? Like in Android is it possible to install just a basic OS onto a phone? one that doesn't have let's say Google ( Google store)? Is there an Android build without Google? Also, does Android have an OS with its own browser, if not, why not? thanks
Dude905 said:
Hello... Since I'm not very familiar with cell phones I'm curious about something. With a desktop computer, one can build their own or have a manufacturer type ( Dell, HP and so ) Now if you take the custom build system you basically can decide which OS you want, why can't cell phones be similar to that be able to install whichever OS you like, Or can you? Like in Android is it possible to install just a basic OS onto a phone? one that doesn't have let's say Google ( Google store)? Is there an Android build without Google? Also, does Android have an OS with its own browser, if not, why not? thanks
Click to expand...
Click to collapse
You're thinking about it along the correct route. There are plain, unbranded Android builds known as Vanilla Android. These are the builds you see on Nexus and Pixel devices, built from the AOSP (Android Open Source Project) and have no carrier or OEM bloat.
If you're looking for a lightweight Android OS with no GApps (Google Apps), there are a ton of custom Android builds available, the most popular in the world being LineageOS. However, it should be noted that you can't simply flash a vanilla or custom Android build to your device and expect it to boot and function properly. Android ROMs need to be ported to a specific device. This is due to the vast hardware differences between various manufacturers and models.
To see if any custom Android builds are available for your particular device, search your model device in the Search Plus option. If any custom ROMs, kernels, recoveries, etc., are available for your device, you'll find them here on XDA.
MotoJunkie01 said:
You're thinking about it along the correct route. There are plain, unbranded Android builds known as Vanilla Android. These are the builds you see on Nexus and Pixel devices, built from the AOSP (Android Open Source Project) and have no carrier or OEM bloat.
If you're looking for a lightweight Android OS with no GApps (Google Apps), there are a ton of custom Android builds available, the most popular in the world being LineageOS. However, it should be noted that you can't simply flash a vanilla or custom Android build to your device and expect it to boot and function properly. Android ROMs need to be ported to a specific device. This is due to the vast hardware differences between various manufacturers and models.
To see if any custom Android builds are available for your particular device, search your model device in the Search Plus option. If any custom ROMs, kernels, recoveries, etc., are available for your device, you'll find them here on XDA.
Click to expand...
Click to collapse
Thank you for your input it gave me more of an understanding and I will do as suggested